ixreport

DigitalOcean: PeeringDB fix list

AS14061 · peeringdb.com/net/6494

PeeringDB

6 things to fix in DigitalOcean's PeeringDB record, from what its exchanges publish: 2 to add, 4 to correct. As of 2026-10-08 22:13 UTC.

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From 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. Netherlands Frys-IX Fryslân, Netherlands · PeeringDB 3512From its IX-F export
    IPv4185.1.160.40
    IPv62001:7f8:10f::36ed:40
    Speed100000 Mbps (100G)
    RS peerYes

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

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. United States DE-CIX Chicago Chicago, United States · PeeringDB 3378
    ProblemPeeringDB hasThe export has
    Port speed differs100G400G
    • In the entry with IPv4 149.112.11.89: set Speed to 400000 (400G) (now 100000).
  2. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 400G
    • In the entry with IPv4 206.82.104.77: set Speed to 400000 (400G) (now 200000).
    • In the entry with IPv4 206.82.104.9: set Speed to 400000 (400G) (now 200000).
  3. ProblemPeeringDB hasThe export has
    Port speed differs2 × 30G2 × 100G
    • In the entry with IPv4 103.77.108.15: set Speed to 100000 (100G) (now 30000).
    • In the entry with IPv4 103.77.108.16: set Speed to 100000 (100G) (now 30000).

    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 differs2 × 100G25G
    • In the entry with IPv4 185.0.20.189: set Speed to 25000 (25G) (now 100000).
    • In the entry with IPv4 185.0.21.19: set Speed to 25000 (25G) (now 100000).

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