ixreport

Telegram Messenger EUR

AS62041

Telegram Messenger Inc

6Exchanges
2On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
OpenPeering policy
4Using the route servers
4To fix in PeeringDB
2Facilities in PeeringDB

Tools: Where can I peer with Telegram Messenger EUR? · Where should Telegram Messenger EUR peer next? · Compare Telegram Messenger EUR with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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
    • 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.31, IPv6 2a03:5f80:4:2::236:31, 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.
    • Add an entry: IPv4 178.18.236.33, IPv6 2a03:5f80:4:2::236:33, 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.

Exchanges over time

0246Oct 3, 2026Nov 19, 20266
Show as a table
DateExchanges
Nov 19, 20266
Nov 18, 20266
Nov 17, 20266
Nov 16, 20266
Nov 15, 20266
Nov 14, 20266
Nov 13, 20266
Nov 12, 20266
Nov 11, 20266
Nov 10, 20266
Nov 9, 20266
Nov 8, 20266
Nov 7, 20266
Nov 6, 20266
Nov 5, 20266
Nov 4, 20266
Nov 3, 20266
Nov 2, 20266
Nov 1, 20266
Oct 31, 20266
Oct 30, 20266
Oct 29, 20266
Oct 28, 20266
Oct 27, 20266
Oct 26, 20266
Oct 25, 20266
Oct 24, 20266
Oct 23, 20266
Oct 22, 20266
Oct 21, 20266
Oct 20, 20266
Oct 19, 20266
Oct 18, 20266
Oct 17, 20266
Oct 16, 20266
Oct 15, 20266
Oct 14, 20266
Oct 13, 20266
Oct 12, 20266
Oct 11, 20266
Oct 10, 20266
Oct 9, 20266
Oct 8, 20266
Oct 7, 20266
Oct 6, 20266
Oct 5, 20266
Oct 4, 20266
Oct 3, 20266

Map

Where Telegram Messenger EUR's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 6.2T, at the 4 of 6 exchanges with a speed in PeeringDB or the exchange's IX-F export.

Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland Not in PeeringDB
Ukraine 1-IX UA Kyiv, Ukraine Not in PeeringDB
Netherlands AMS-IX Amsterdam, Netherlands 80.249.209.69
80.249.214.57
80.249.214.80
80.249.214.239
2001:7f8:1::a506:2041:1
2001:7f8:1::a506:2041:2
2001:7f8:1::a506:2041:3
2001:7f8:1::a506:2041:4
4 × 400G 92 routes Both
Germany DE-CIX Frankfurt Frankfurt, Germany 80.81.193.148
80.81.196.155
80.81.196.179
80.81.196.184
2001:7f8::f259:0:1
2001:7f8::f259:0:2
2001:7f8::f259:0:3
2001:7f8::f259:0:4
4 × 400G 96 routes Both Speed differs
Netherlands Global-IX Amsterdam, Netherlands 109.239.136.22 2001:b28:3ff::f259:2 600G Yes PeeringDB
Netherlands GNM-IX Amsterdam, Netherlands 178.18.225.141
178.18.226.168
178.18.227.6
178.18.227.113
2a03:5f80:4::225:141
2a03:5f80:4::226:168
2a03:5f80:4::227:6
2a03:5f80:4::227:113
4 × 600G Yes Both IPv4 not in PeeringDBIPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (10)

These exchanges have a switch in a facility where Telegram Messenger EUR lists itself in PeeringDB, but don't have Telegram Messenger EUR as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

Netherlands NL-ixAmsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands 672 Equinix AM5 - Amsterdam, Schepenbergweg
Netherlands Frys-IXFryslân, Netherlands 338 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Netherlands INTERIXAmsterdam, Netherlands 262 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Netherlands ERA-IX AmsterdamAmsterdam, Netherlands 244 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Bulgaria NetIXSofia, Bulgaria 204 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
France nineAmsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France 160 Equinix AM5 - Amsterdam, Schepenbergweg
Netherlands LSIXAmsterdam, The Hague, Rotterdam, Naaldwijk, Netherlands 105 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Netherlands 1-NL FREEAmsterdam, Netherlands 60 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Netherlands Equinix AmsterdamAmsterdam, Netherlands 51 Equinix AM5 - Amsterdam, Schepenbergweg; Equinix AM4 - Amsterdam, Science Park
Romania Balcan-IXBucharest, Romania 29 Equinix AM5 - Amsterdam, Schepenbergweg
Facilities (2)

The buildings Telegram Messenger EUR lists in PeeringDB, and how many of the exchanges in each it's on.

Netherlands Equinix AM5 - Amsterdam, SchepenbergwegAmsterdam 4 of 14
Netherlands Equinix AM4 - Amsterdam, Science ParkAmsterdam 3 of 10