OVHcloud: PeeringDB fix list

AS16276 · peeringdb.com/net/1264

PeeringDB

18 things to fix in OVHcloud's PeeringDB record, from what its exchanges publish: 2 to add, 6 to correct, 4 to check, 6 at exchanges that look shut down. As of 2026-10-08 20:58 UTC.

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

  1. Ukraine 1-IX UA Kyiv, Ukraine · PeeringDB 3562From 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. France DE-CIX Marseille Marseille, France · PeeringDB 1149From its IX-F export and website members list
    IPv4185.1.47.56
    IPv62001:7f8:36::3f94:0:1
    Speed100000 Mbps (100G)
    RS peerYes

Correct these entries (6)

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. Canada CANIX Montreal Montreal, Canada · PeeringDB 355
    ProblemPeeringDB hasThe export has
    Port speed differs200G100G
    • In the entry with IPv4 198.179.18.33: set Speed to 100000 (100G) (now 200000).

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

  2. United States CIX-NoVA Ashburn, Reston, Washington DC, United States · PeeringDB 4796
    ProblemPeeringDB hasThe export has
    Port speed differs400G100G
    • In the entry with IPv4 149.112.69.15: set Speed to 100000 (100G) (now 400000).
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 800G2 × 1.2T
    • In the entry with IPv4 80.81.192.209: set Speed to 1200000 (1.2T) (now 800000).
    • In the entry with IPv4 80.81.193.209: set Speed to 1200000 (1.2T) (now 800000).
  4. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    Port speed differs100G200G
    • In the entry with IPv4 185.1.240.176: 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.

  5. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs4 × 400G + 2 × 100G2 × 400G + 100G

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

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

Check these entries (4)

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

  1. United States ChIX Chicago, United States · PeeringDB 239Not on its website members list
    IPv4206.41.110.218
    IPv62001:504:41:110::218
    Speed100000 Mbps (100G)

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

  2. Germany MegaIX Dusseldorf Dusseldorf, Germany · PeeringDB 91Not on its IX-F export
    IPv4194.146.118.31
    IPv62001:7f8:8::3f94:0:1
    Speed100000 Mbps (100G)
  3. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.176
    IPv62001:7f8:d:fe::176
    Speed100000 Mbps (100G)
  4. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.176
    IPv62001:7f8:d:ff::176
    Speed100000 Mbps (100G)

Exchanges that look shut down (6)

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. United States MegaIX Bostonghost Boston, United States · PeeringDB 5061

    Only one outside network

    IPv4206.53.168.73
    IPv62606:a980:0:10::9
    Speed100000 Mbps (100G)
  2. Ireland MegaIX Dublinghost Dublin, Ireland · PeeringDB 4710

    Only one outside network

    IPv4194.59.191.9
    IPv62001:7f8:8:2::9
    Speed100000 Mbps (100G)
  3. Spain MegaIX Madridghost Madrid, Spain · PeeringDB 5063

    Only one outside network

    IPv4194.59.191.201
    IPv62001:7f8:8:1::9
    Speed100000 Mbps (100G)
  4. Italy MegaIX Milanghost Milan, Italy · PeeringDB 5060

    Only one outside network

    IPv4194.59.191.137
    IPv62001:7f8:8:3::9
    Speed100000 Mbps (100G)
  5. Canada MegaIX Montrealghost Montreal, Canada · PeeringDB 4712

    Only one outside network

    IPv4206.53.168.199
    IPv62606:a980:0:1::7
    Speed100000 Mbps (100G)
  6. United States MegaIX Portlandghost Portland, United States · PeeringDB 5059

    Only one outside network

    IPv4206.53.169.200
    IPv62606:a980:0:12::8
    Speed100000 Mbps (100G)

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