Baffin Bay Networks: PeeringDB fix list

AS42649 · peeringdb.com/net/13688

PeeringDB

9 things to fix in Baffin Bay Networks's PeeringDB record, from what its exchanges publish: 3 to add, 6 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Baffin Bay Networks'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 (3)

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

  1. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.15
    IPv62001:7f8:d:fb::15
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.15
    IPv62001:7f8:d:fc::15
    SpeedNot published
    RS peerYes
  3. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587From its IX-F export
    IPv4185.1.8.138
    IPv62001:7f8:73::a699:0:1
    Speed10000 Mbps (10G)
    RS peerYes

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.170.102: set Speed to 100000 (100G) (now 10000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.210.114: set Speed to 100000 (100G) (now 10000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 185.1.208.111: set Speed to 100000 (100G) (now 10000).
  4. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 206.82.105.1: set Speed to 200000 (200G) (now 10000).
  5. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.128.15 194.68.128.134194.68.128.15
    IPv6 address in PeeringDB, not in the export2001:7f8:d:fe::15 2001:7f8:d:fe::1342001:7f8:d:fe::15
    • The entry with IPv4 194.68.128.134, IPv6 2001:7f8:d:fe::134 isn't in the export: delete it if that connection is gone.
  6. ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export194.68.123.15 194.68.123.134194.68.123.15
    IPv6 address in PeeringDB, not in the export2001:7f8:d:ff::15 2001:7f8:d:ff::1342001:7f8:d:ff::15
    • The entry with IPv4 194.68.123.134, IPv6 2001:7f8:d:ff::134 isn't in the export: delete it if that connection is gone.

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