ixreport

EXATEL SA: PeeringDB fix list

AS20804 · peeringdb.com/net/6350

PeeringDB

11 things to fix in EXATEL SA's PeeringDB record, from what its exchanges publish: 2 to add, 8 to correct, 1 to check. As of 2026-10-08 18:53 UTC.

Make the changes on EXATEL 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 (2)

On the exchange's own member list, but not in EXATEL SA'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. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.209.253
    IPv62001:7f8:20:101::209:253
    SpeedNot published
    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 (8)

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. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.170.104: set Speed to 100000 (100G) (now 1000).
  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs20G100G
    • In the entry with IPv4 80.81.192.124: set Speed to 100000 (100G) (now 20000).
  3. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.210.117: set Speed to 100000 (100G) (now 1000).
  4. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.47.123: set Speed to 100000 (100G) (now 1000).
  5. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.208.113: set Speed to 100000 (100G) (now 1000).
  6. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs10G10T
    • In the entry with IPv4 194.68.123.167: set Speed to 10000000 (10T) (now 10000).
  7. Czechia NIX.CZ Prague, Czechia · PeeringDB 71
    ProblemPeeringDB hasThe export has
    Port speed differs10G25G
    • In the entry with IPv4 91.210.17.19: set Speed to 25000 (25G) (now 10000).

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

  8. Poland THINX Warsaw Warsaw, Poland · PeeringDB 481
    ProblemPeeringDB hasThe export has
    Port speed differs100G + 40G110G
    • In the entry with IPv4 212.91.0.220: set Speed to 110000 (110G) (now 40000).
    • In the entry with IPv4 212.91.0.34: set Speed to 110000 (110G) (now 100000).
    • Add an entry: IPv4 212.91.0.220, IPv6 –, speed 110000 (110G).
    • Add an entry: IPv4 212.91.0.34, IPv6 –, speed 110000 (110G).

    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 (1)

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

  1. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321Not on its IX-F export or website members list
    IPv4195.66.239.40
    IPv62001:7f8:4:1::5144:1
    Speed1000 Mbps (1G)

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