Orange CDN: PeeringDB fix list

AS328126 · peeringdb.com/net/21589

PeeringDB

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

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

  1. Hungary BIX Budapest, Hungary · PeeringDB 55From its IX-F export
    IPv4193.188.137.79
    IPv62001:7f8:35::32:8126:1
    Speed10000 Mbps (10G)
    RS peerYes
  2. Italy Namex Rome Rome, Italy · PeeringDB 121From its IX-F export

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

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

  3. United Arab Emirates SH-IX Fujairah, United Arab Emirates · PeeringDB 866From its website members list
    IPv4185.1.15.49
    IPv62001:7f8:7a::32:8126:1
    SpeedNot published
    RS peerNot published
  4. United Arab Emirates UAE-IX Dubai, United Arab Emirates · PeeringDB 587From its IX-F export and website members list
    IPv4185.1.8.109
    IPv62001:7f8:73:0:5:1be:0:1
    Speed10000 Mbps (10G)
    RS peerYes

Correct these entries (2)

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. South Africa NAPAfrica IX Cape Town Cape Town, South Africa · PeeringDB 597
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d1::200
    Port speed differs10G20G
    • In the entry with IPv4 196.60.70.200: set IPv6 to 2001:43f8:6d1::200 (now empty); set Speed to 20000 (20G) (now 10000).

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

  2. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:43f8:6d0::9:200
    Port speed differs10G20G
    • In the entry with IPv4 196.60.9.200: set IPv6 to 2001:43f8:6d0::9:200 (now empty); set Speed to 20000 (20G) (now 10000).

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

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