Telegram Messenger APAC: PeeringDB fix list
AS62014 · peeringdb.com/net/23350
2 things to fix in Telegram Messenger APAC's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Telegram Messenger APAC'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 (1)
On the exchange's own member list, but not in Telegram Messenger APAC's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 103.162.254.119 IPv6 2001:df6:480::f23e:0:1 Speed 200000 Mbps (200G) RS peer Yes IPv4 103.162.254.120 IPv6 2001:df6:480::f23e:0:2 Speed 200000 Mbps (200G) RS peer Yes
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 Port speed differs 2 × 200G 2 × 400G - In the entry with IPv4 103.16.102.233: set Speed to 400000 (400G) (now 200000).
- In the entry with IPv4 103.16.102.92: set Speed to 400000 (400G) (now 200000).
From ixreport.com/net/62014/: 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.