ixreport

Telegram Messenger NA

AS59930

Telegram Messenger Inc

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
ContentType
SelectivePeering policy
3Using the route servers
1To fix in PeeringDB
0Facilities in PeeringDB

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

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

PeeringDB fix list Printable page · CSV

One thing to fix in Telegram Messenger NA's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 18:41 UTC.

Make the changes on Telegram Messenger NA'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 (1)

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. United States FL-IX Miami, United States · PeeringDB 954
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB206.41.108.63206.41.108.63 206.41.108.198
    IPv6 address missing from PeeringDB2001:504:40:108::1:632001:504:40:108::1:63 2001:504:40:108::1:198
    Port speed differs100G2 × 100G
    • Add an entry: IPv4 206.41.108.198, IPv6 2001:504:40:108::1:198, speed 100000 (100G), RS peer yes.

Exchanges over time

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

Map

Where Telegram Messenger NA'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 500G across 3 exchanges.

United States Equinix Miami Miami, United States 198.32.242.10 2001:504:0:6:0:5:9930:2 200G Yes PeeringDB
United States FL-IX Miami, United States 206.41.108.63 2001:504:40:108::1:63 100G 4 routes Both IPv4 not in PeeringDBIPv6 not in PeeringDBSpeed differs
Brazil IX.br (PTT.br) São Paulo São Paulo/SP, Brazil 187.16.209.180 2001:12f8::209:180 200G 6 routes Both

Telegram Messenger NA lists no facilities in PeeringDB.