Telegram Messenger NA: PeeringDB fix list
AS59930 · peeringdb.com/net/19770
One thing to fix in Telegram Messenger NA's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB 206.41.108.63 206.41.108.63 206.41.108.198 IPv6 address missing from PeeringDB 2001:504:40:108::1:63 2001:504:40:108::1:63 2001:504:40:108::1:198 Port speed differs 100G 2 × 100G - Add an entry: IPv4 206.41.108.198, IPv6 2001:504:40:108::1:198, speed 100000 (100G), RS peer yes.
From ixreport.com/net/59930/: 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.