Telegram Messenger EUR: PeeringDB fix list

AS62041 · peeringdb.com/net/13649

PeeringDB

4 things to fix in Telegram Messenger EUR's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 20:58 UTC.

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From 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. 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 (2)

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
    Port speed differs4 × 400G4 × 600G
    • In the entry with IPv4 80.81.193.148: set Speed to 600000 (600G) (now 400000).
    • In the entry with IPv4 80.81.196.155: set Speed to 600000 (600G) (now 400000).
    • In the entry with IPv4 80.81.196.179: set Speed to 600000 (600G) (now 400000).
    • In the entry with IPv4 80.81.196.184: set Speed to 600000 (600G) (now 400000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.141 178.18.226.168 178.18.227.6 178.18.227.113178.18.225.141 178.18.226.168 178.18.227.6 178.18.227.113 178.18.236.31 178.18.236.32 178.18.236.33 178.18.236.34
    IPv6 address missing from PeeringDB2a03:5f80:4::225:141 2a03:5f80:4::226:168 2a03:5f80:4::227:6 2a03:5f80:4::227:1132a03:5f80:4::225:141 2a03:5f80:4::226:168 2a03:5f80:4::227:6 2a03:5f80:4::227:113 2a03:5f80:4:2::236:31 2a03:5f80:4:2::236:32 2a03:5f80:4:2::236:33 2a03:5f80:4:2::236:34
    Port speed differs4 × 600G800G + 3 × 600G
    • In the entry with IPv4 178.18.226.168: set Speed to 800000 (800G) (now 600000).
    • Add an entry: IPv4 178.18.236.31, IPv6 2a03:5f80:4:2::236:31, speed 800000 (800G), RS peer yes.
    • Add an entry: IPv4 178.18.236.32, IPv6 2a03:5f80:4:2::236:32, speed 600000 (600G), RS peer yes.
    • Add an entry: IPv4 178.18.236.33, IPv6 2a03:5f80:4:2::236:33, speed 600000 (600G), RS peer yes.
    • Add an entry: IPv4 178.18.236.34, IPv6 2a03:5f80:4:2::236:34, speed 600000 (600G), 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.

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