ixreport

ISTQSERVERS: PeeringDB fix list

AS211826 · peeringdb.com/net/29941

PeeringDB

5 things to fix in ISTQSERVERS's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct, 1 to check. As of 2026-10-08 22:13 UTC.

Make the changes on ISTQSERVERS'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 ISTQSERVERS'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.

Correct these entries (3)

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 Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::3:3b72:0:1
    • In the entry with IPv4 80.81.192.11: set IPv6 to 2001:7f8::3:3b72:0:1 (now empty).
  2. Netherlands ERA-IX Amsterdam Amsterdam, Netherlands · PeeringDB 3789
    ProblemPeeringDB hasThe export has
    Port speed differs300G200G
    • In the entry with IPv4 185.1.240.43: set Speed to 200000 (200G) (now 300000).

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

  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.41178.18.224.60 178.18.236.41
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:412a03:5f80:4::224:60 2a03:5f80:4:2::236:41
    • Add an entry: IPv4 178.18.224.60, IPv6 2a03:5f80:4::224:60, speed 100000 (100G), RS peer yes.

    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 ISTQSERVERS has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713Not on its IX-F export or website members list
    IPv4185.0.21.30
    IPv6–
    Speed10000 Mbps (10G)
    IPv4185.0.21.64
    IPv62001:7f8:7f::c:64
    Speed100000 Mbps (100G)

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