ixreport

DE-CIX Monitoring: PeeringDB fix list

AS205529 · peeringdb.com/net/36819

PeeringDB

11 things to fix in DE-CIX Monitoring's PeeringDB record, from what its exchanges publish: 4 to correct, 5 to check, 2 at exchanges that look shut down. As of 2026-10-08 22:13 UTC.

Make the changes on DE-CIX Monitoring'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 (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. Brunei Borneo-IX Bandar Seri Begawan, Brunei · PeeringDB 3440
    ProblemPeeringDB hasThe export has
    Port speed differs20G2G
    • In the entry with IPv4 103.162.82.249: set Speed to 2000 (2G) (now 20000).
  2. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2607:1780:8000:c64:6:1ca4:c:1
    • In the entry with IPv4 216.59.36.249: set IPv6 to 2607:1780:8000:c64:6:1ca4:c:1 (now empty).
  3. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB206.53.202.252 is AS62499 DE-CIX Dallas Route Servers206.53.202.252
    Address belongs to another network in PeeringDB2001:504:61::f423:fc:1 is AS62499 DE-CIX Dallas Route Servers2001:504:61::f423:fc:1
    Port speed differs20G2 × 20G

    An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.

    • Add an entry: IPv4 –, IPv6 –, speed 20000 (20G), RS peer no.
  4. Greece SEECIX Athens, Greece · PeeringDB 3184
    ProblemPeeringDB hasThe export has
    Port speed differs20G2G
    • In the entry with IPv4 185.1.172.249: set Speed to 2000 (2G) (now 20000).

Check these entries (5)

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

  1. Jordan Aqaba IX Aqaba, Jordan · PeeringDB 3366Not on its website members list
    IPv484.252.106.249
    IPv62a10:1100::3:2a9b:c:1
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  2. Indonesia DE-CIX Jakarta Jakarta, Indonesia · PeeringDB 4411Not on its IX-F export or website members list
    IPv449.213.56.249
    IPv62001:df5:7880::2614:c:1
    Speed20000 Mbps (20G)
  3. Brazil DE-CIX Rio de Janeiro Rio de Janeiro, Brazil · PeeringDB 4641Not on its website members list
    IPv445.68.93.249
    IPv62801:81:c0:2:4:310f:c:1
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  4. Brazil DE-CIX Sao Paulo Sao Paulo, Brazil · PeeringDB 4642Not on its website members list
    IPv445.68.92.249
    IPv62801:81:c0:1:4:30fa:c:1
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

  5. Pakistan Pakistan Internet Exchange (PIE) Karachi Karachi, Pakistan · PeeringDB 4271Not on its website members list
    IPv458.181.127.249
    IPv62001:df2:b940:0:2:2413:c:1
    Speed20000 Mbps (20G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

Exchanges that look shut down (2)

In PeeringDB, but these exchanges have fewer than two networks besides their operator: nobody to peer with, so they may have shut down. If an exchange is gone, delete its entry.

  1. Only the operator's own networks

    IPv4216.59.37.249
    IPv62607:1780:8000:c1d:6:1ca5:c:1
    Speed20000 Mbps (20G)
  2. Only one outside network

    IPv4185.0.8.121
    IPv62001:7f8:13e:0:3:12c2:c:1
    Speed20000 Mbps (20G)

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