ixreport

Bink Group: PeeringDB fix list

AS8282 · peeringdb.com/net/1101

PeeringDB

2 things to fix in Bink Group's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Bink Group's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Bink Group's PeeringDB record. Add one entry per connection with these values.

  1. United Kingdom LONAP London, United Kingdom · PeeringDB 53From its IX-F export
    IPv45.57.80.67
    IPv62001:7f8:17::205a:1
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

Correct these entries (1)

Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs10G2G
    • In the entry with IPv4 195.66.237.155: set Speed to 2000 (2G) (now 10000).

From ixreport.com/net/8282/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.