ixreport

Blizzard Entertainment: PeeringDB fix list

AS57976 · peeringdb.com/net/5886

PeeringDB

7 things to fix in Blizzard Entertainment's PeeringDB record, from what its exchanges publish: 2 to add, 5 to correct. As of 2026-10-08 21:56 UTC.

Make the changes on Blizzard Entertainment'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 (2)

On the exchange's own member list, but not in Blizzard Entertainment'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.6
    IPv62001:7f8:d:fb::6
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.6
    IPv62001:7f8:d:fc::6
    SpeedNot published
    RS peerYes

Correct these entries (5)

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 differs10G200G
    • In the entry with IPv4 185.1.170.112: set Speed to 200000 (200G) (now 10000).
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.210.123: set Speed to 200000 (200G) (now 10000).
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 185.1.208.122: set Speed to 200000 (200G) (now 10000).
  4. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.172 178.18.236.78178.18.225.172 178.18.236.78 178.18.236.247
    IPv6 address missing from PeeringDB2a03:5f80:4::225:172 2a03:5f80:4:2::236:782a03:5f80:4::225:172 2a03:5f80:4:2::236:78 2a03:5f80:4:2::236:247
    • Add an entry: IPv4 178.18.236.247, IPv6 2a03:5f80:4:2::236:247, speed 100000 (100G), RS peer yes.

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

  5. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.20.193: set Speed to 12500 (12.5G) (now 100000).

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