IP-Max SA: PeeringDB fix list

AS25091 · peeringdb.com/net/1452

PeeringDB

21 things to fix in IP-Max SA's PeeringDB record, from what its exchanges publish: 1 to add, 15 to correct, 5 to check. As of 2026-10-08 20:58 UTC.

Make the changes on IP-Max SA'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 (1)

On the exchange's own member list, but not in IP-Max SA's PeeringDB record. Add one entry per connection with these values.

  1. France Hopus Paris, Lyon, Marseille, Geneva, Zurich, Amsterdam, Frankfurt, France · PeeringDB 1320From 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.

Correct these entries (15)

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. Spain DE-CIX Barcelona Barcelona, Spain · PeeringDB 3446
    ProblemPeeringDB hasThe export has
    Port speed differs100M10G
    • In the entry with IPv4 185.1.119.37: set Speed to 10000 (10G) (now 100).
  2. United States DE-CIX Chicago Chicago, United States · PeeringDB 3378
    ProblemPeeringDB hasThe export has
    Port speed differs100M10G
    • In the entry with IPv4 149.112.11.100: set Speed to 10000 (10G) (now 100).
  3. United States DE-CIX Dallas Dallas, United States · PeeringDB 1249
    ProblemPeeringDB hasThe export has
    Port speed differs200M10G
    • In the entry with IPv4 206.53.202.64: set Speed to 10000 (10G) (now 200).
  4. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G200G
    • In the entry with IPv4 80.81.193.46: set Speed to 200000 (200G) (now 10000).
  5. Türkiye DE-CIX Istanbul Istanbul, Türkiye · PeeringDB 1150
    ProblemPeeringDB hasThe export has
    Port speed differs500M10G
    • In the entry with IPv4 185.1.48.7: set Speed to 10000 (10G) (now 500).
  6. Portugal DE-CIX Lisbon Lisbon, Portugal · PeeringDB 2531
    ProblemPeeringDB hasThe export has
    Port speed differs500M10G
    • In the entry with IPv4 185.1.131.52: set Speed to 10000 (10G) (now 500).
  7. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs500M10G
    • In the entry with IPv4 185.1.192.140: set Speed to 10000 (10G) (now 500).
  8. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs2G10G
    • In the entry with IPv4 185.1.47.80: set Speed to 10000 (10G) (now 2000).
  9. United States DE-CIX New York New York, United States · PeeringDB 804
    ProblemPeeringDB hasThe export has
    Port speed differs500M10G
    • In the entry with IPv4 206.82.104.143: set Speed to 10000 (10G) (now 500).
  10. Italy DE-CIX Palermo Palermo, Italy · PeeringDB 1131
    ProblemPeeringDB hasThe export has
    Port speed differs100M10G
    • In the entry with IPv4 185.1.46.24: set Speed to 10000 (10G) (now 100).
  11. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G4G
    • In the entry with IPv4 195.66.225.82: set Speed to 4000 (4G) (now 10000).
  12. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    Port speed differs1G100M
    • In the entry with IPv4 188.93.170.71: set Speed to 100 (100M) (now 1000).

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

  13. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 194.68.128.78: set Speed to 200000 (200G) (now 1000).
  14. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs1G200G
    • In the entry with IPv4 194.68.123.78: set Speed to 200000 (200G) (now 1000).
  15. Switzerland SwissIX Zurich, Switzerland · PeeringDB 60
    ProblemPeeringDB hasThe export has
    Port speed differs20G + 10G100G + 20G
    • In the entry with IPv4 91.206.53.48: set Speed to 100000 (100G) (now 10000).

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

Check these entries (5)

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

  1. Russia MSK-IX Ekaterinburg Ekaterinburg, Russia · PeeringDB 350Not on its IX-F export
    IPv4194.85.107.93
    IPv62001:7f8:20:301::107:93
    Speed1000 Mbps (1G)
  2. Russia MSK-IX Novosibirsk Novosibirsk, Russia · PeeringDB 223Not on its IX-F export
    IPv4193.232.87.193
    IPv62001:7f8:20:401::87:193
    Speed1000 Mbps (1G)
  3. Russia MSK-IX Rostov-on-Don Rostov-on-Don, Russia · PeeringDB 380Not on its IX-F export
    IPv4193.232.140.93
    IPv62001:7f8:20:501::140:93
    Speed1000 Mbps (1G)
  4. Russia MSK-IX Saint-Petersburg St.Petersburg, Russia · PeeringDB 107Not on its IX-F export
    IPv4194.226.101.93
    IPv62001:7f8:20:201::101:93
    Speed1000 Mbps (1G)
    IPv4194.226.103.93
    IPv62001:7f8:20:202::103:93
    Speed1000 Mbps (1G)
  5. Russia MSK-IX Vladivostok Vladivostok, Russia · PeeringDB 378Not on its IX-F export
    IPv4193.232.136.93
    IPv62001:7f8:20:701::136:93
    Speed1000 Mbps (1G)

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