Telehouse: PeeringDB fix list

AS57344 · peeringdb.com/net/4977

PeeringDB

13 things to fix in Telehouse's PeeringDB record, from what its exchanges publish: 13 to correct. As of 2026-10-08 21:35 UTC.

Make the changes on Telehouse's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Correct these entries (13)

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. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.30.26 185.1.30.40 185.1.30.45 185.1.30.57 185.1.30.58 185.1.30.85 185.1.30.111 185.1.30.116 185.1.30.120 185.1.30.126 185.1.30.143 185.1.30.144185.1.30.26 185.1.30.40 185.1.30.45 185.1.30.57 185.1.30.58 185.1.30.111 185.1.30.116 185.1.30.120 185.1.30.126 185.1.30.143 185.1.30.144
    Port speed differs12 × 470G470G
    • In the entry with IPv4 185.1.30.85: set IPv4 to (empty) (now 185.1.30.85).
  2. Hungary BIX Budapest, Hungary · PeeringDB 55
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:35::5:7344:1
    • In the entry with IPv4 193.188.137.166: set IPv6 to 2001:7f8:35::5:7344:1 (now empty).
  3. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.166 193.169.198.170 193.169.198.171 193.169.198.203 193.169.198.204193.169.198.166 193.169.198.168 193.169.198.170 193.169.198.171 193.169.198.203 193.169.198.204 193.169.198.218 193.169.198.219
    IPv6 address missing from PeeringDBnone2001:7f8:58::e000:0:1
    • In the entry with IPv4 193.169.198.166: set IPv6 to 2001:7f8:58::e000:0:1 (now empty).
    • Add an entry: IPv4 193.169.198.168, IPv6 –.
    • Add an entry: IPv4 193.169.198.218, IPv6 –.
    • Add an entry: IPv4 193.169.198.219, IPv6 –.
  4. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.170.235: set Speed to 100000 (100G) (now 1000).
  5. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.210.204: set Speed to 100000 (100G) (now 1000).
  6. Spain DE-CIX Madrid Madrid, Spain · PeeringDB 1277
    ProblemPeeringDB hasThe export has
    Port speed differs2G100G
    • In the entry with IPv4 185.1.192.241: set Speed to 100000 (100G) (now 2000).
  7. Germany DE-CIX Munich Munich, Germany · PeeringDB 248
    ProblemPeeringDB hasThe export has
    Port speed differs1G100G
    • In the entry with IPv4 185.1.208.213: set Speed to 100000 (100G) (now 1000).
  8. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  9. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  10. Romania InterLAN-IX Bucharest, Romania · PeeringDB 270
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G20G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  11. Netherlands LSIX Amsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands · PeeringDB 1308
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G
  12. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G13.75G
    • In the entry with IPv4 185.0.20.82: set Speed to 13750 (13.75G) (now 100000).
  13. Netherlands Speed-IX Dronten, Netherlands · PeeringDB 1842
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 10G10G

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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