i3D.net: PeeringDB fix list

AS49544 · peeringdb.com/net/2496

PeeringDB

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

Make the changes on i3D.net'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 i3D.net's PeeringDB record. Add one entry per connection with these values.

  1. India AMS-IX Mumbai Mumbai, India · PeeringDB 1623From its IX-F export
    IPv4223.31.200.103
    IPv62001:e48:44:100b:0:a504:9544:1
    Speed10000 Mbps (10G)
    RS peerNo

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

  2. India DE-CIX Mumbai Mumbai, India · PeeringDB 832From 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.76
    IPv62001:7f8:d:fb::76
    SpeedNot published
    RS peerYes
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.76
    IPv62001:7f8:d:fc::76
    SpeedNot published
    RS peerYes

Correct these entries (4)

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. Poland EPIX.Katowice Katowice/Silesia, Poland · PeeringDB 491
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 178.216.40.248: set Speed to 100000 (100G) (now 40000).

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

  2. Poland EPIX.Warszawa Warsaw, Poland · PeeringDB 474
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 89.46.144.171: set Speed to 100000 (100G) (now 40000).

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

  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.239.117.76193.239.117.76 193.239.119.3
    IPv6 address missing from PeeringDB2001:7f8:13::a504:9544:12001:7f8:13::a504:9544:1 2001:7f8:13::a504:9544:3
    • Add an entry: IPv4 193.239.119.3, IPv6 2001:7f8:13::a504:9544:3, 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.

  4. 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.153: set Speed to 12500 (12.5G) (now 100000).

Check these entries (1)

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

  1. Germany City-IX Frankfurt Frankfurt, Germany · PeeringDB 4175Not on its IX-F export
    IPv4185.0.10.78
    IPv62001:7f8:e2::a504:9544:1
    Speed100000 Mbps (100G)

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