AT&T EMEA: PeeringDB fix list

AS2686 · peeringdb.com/net/670

PeeringDB

4 things to fix in AT&T EMEA's PeeringDB record, from what its exchanges publish: 2 to correct, 2 to check. As of 2026-10-08 20:58 UTC.

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

Correct these entries (2)

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. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 193.188.137.86: set Speed to 10000 (10G) (now 20000).
  2. Belgium BNIX Brussels, Belgium · PeeringDB 59
    ProblemPeeringDB hasThe export has
    Port speed differs10G20G
    • In the entry with IPv4 194.53.172.77: set Speed to 20000 (20G) (now 10000).

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

Check these entries (2)

In PeeringDB, but on none of the exchange's own lists. If AT&T EMEA has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.44
    IPv62001:7f8:d:fe::44
    Speed10000 Mbps (10G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.44
    IPv62001:7f8:d:ff::44
    Speed10000 Mbps (10G)

From ixreport.com/net/2686/: 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.