ixreport

CDN77: PeeringDB fix list

AS60068 · peeringdb.com/net/10839

PeeringDB

7 things to fix in CDN77'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 CDN77'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 CDN77's PeeringDB record. Add one entry per connection with these values.

  1. Brazil IX.br (PTT.br) Fortaleza Fortaleza/CE, Brazil · PeeringDB 710From 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. Singapore SGIX Singapore, Singapore · PeeringDB 429From its IX-F export and website members list
    IPv4103.16.102.223
    IPv62001:de8:12:100::223
    Speed200000 Mbps (200G)
    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. Nigeria AMS-IX Lagos Lagos, Nigeria · PeeringDB 2381
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 196.60.58.245: set Speed to 200000 (200G) (now 100000).

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

  2. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:8e:4::77
    • Add an entry: IPv4 –, IPv6 2001:7f8:8e:4::77, speed 100000 (100G), RS peer yes.
  3. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 185.1.240.32: set Speed to 200000 (200G) (now 100000).

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

  4. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 217.29.66.31: set Speed to 200000 (200G) (now 100000).
  5. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs3 × 200G + 4 × 100G550G
    • In the entry with IPv4 185.0.20.105: set Speed to 550000 (550G) (now 200000).
    • In the entry with IPv4 185.0.20.13: set Speed to 550000 (550G) (now 200000).
    • In the entry with IPv4 185.0.20.192: set Speed to 550000 (550G) (now 100000).
    • In the entry with IPv4 185.0.20.200: set Speed to 550000 (550G) (now 200000).
    • In the entry with IPv4 185.0.20.27: set Speed to 550000 (550G) (now 100000).
    • In the entry with IPv4 185.0.20.28: set Speed to 550000 (550G) (now 100000).
    • In the entry with IPv4 185.0.20.29: set Speed to 550000 (550G) (now 100000).

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