BT: PeeringDB fix list

AS5400 · peeringdb.com/net/118

PeeringDB

11 things to fix in BT's PeeringDB record, from what its exchanges publish: 4 to add, 6 to correct, 1 to check. As of 2026-10-08 20:58 UTC.

Make the changes on BT'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 (4)

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

  1. Finland FICIX 2 (Helsinki) Helsinki, Finland · PeeringDB 98From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Japan JPIX TOKYO Tokyo, Japan · PeeringDB 30From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  3. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.106
    IPv62001:7f8:d:fb::106
    SpeedNot published
    RS peerNo
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.106
    IPv62001:7f8:d:fc::106
    SpeedNot published
    RS peerNo

Correct these entries (6)

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 differs1G10G
    • In the entry with IPv4 193.188.137.53: set Speed to 10000 (10G) (now 1000).
  2. Denmark Netnod Copenhagen BLUE -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 2868
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export212.237.192.25 212.237.192.26 212.237.192.109212.237.192.25
    IPv6 address in PeeringDB, not in the export2001:7f8:d:202::25 2001:7f8:d:202::26 2001:7f8:d:202::1092001:7f8:d:202::25
    • The entry with IPv4 212.237.192.109, IPv6 2001:7f8:d:202::109 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 212.237.192.26, IPv6 2001:7f8:d:202::26 isn't in the export: delete it if that connection is gone.
  3. Denmark Netnod Copenhagen GREEN -- MTU9K Malmo / Copenhagen, Denmark · PeeringDB 193
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export212.237.193.25 212.237.193.26 212.237.193.109212.237.193.25
    IPv6 address in PeeringDB, not in the export2001:7f8:d:203::25 2001:7f8:d:203::26 2001:7f8:d:203::1092001:7f8:d:203::25
    • The entry with IPv4 212.237.193.109, IPv6 2001:7f8:d:203::109 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 212.237.193.26, IPv6 2001:7f8:d:203::26 isn't in the export: delete it if that connection is gone.
  4. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.128.106 194.68.128.109 194.68.128.199194.68.128.106
    IPv6 address in PeeringDB, not in the export2001:7f8:d:fe::106 2001:7f8:d:fe::109 2001:7f8:d:fe::1992001:7f8:d:fe::106
    • The entry with IPv4 194.68.128.109, IPv6 2001:7f8:d:fe::109 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 194.68.128.199, IPv6 2001:7f8:d:fe::199 isn't in the export: delete it if that connection is gone.
  5. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.123.106 194.68.123.109 194.68.123.199194.68.123.106
    IPv6 address in PeeringDB, not in the export2001:7f8:d:ff::106 2001:7f8:d:ff::109 2001:7f8:d:ff::1992001:7f8:d:ff::106
    • The entry with IPv4 194.68.123.109, IPv6 2001:7f8:d:ff::109 isn't in the export: delete it if that connection is gone.
    • The entry with IPv4 194.68.123.199, IPv6 2001:7f8:d:ff::199 isn't in the export: delete it if that connection is gone.
  6. Switzerland SwissIX Zurich, Switzerland · PeeringDB 60
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB91.206.52.17491.206.52.138 91.206.52.174
    IPv6 address missing from PeeringDB2001:7f8:24::1518:0:12001:7f8:24::8a 2001:7f8:24::1518:0:1
    Port speed differs100G100G + 10G
    • Add an entry: IPv4 91.206.52.138, IPv6 2001:7f8:24::8a, speed 10000 (10G), RS peer no.

    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 (1)

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

  1. United States SIX Seattle Seattle, United States · PeeringDB 13Not on its IX-F export or website members list
    IPv4206.81.82.49
    IPv62001:504:16::1518
    Speed100000 Mbps (100G)

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