ixreport

Telegram Messenger APAC

AS62014

Telegram Messenger Inc

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

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

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

PeeringDB fix list Printable page · CSV

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-11-19 12:40 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.

  1. Singapore DE-CIX ASEAN Singapore, Singapore · PeeringDB 3472From its IX-F export and website members list

    2 connections, so 2 entries:

    IPv4103.162.254.119
    IPv62001:df6:480::f23e:0:1
    Speed200000 Mbps (200G)
    RS peerYes
    IPv4103.162.254.120
    IPv62001:df6:480::f23e:0:2
    Speed200000 Mbps (200G)
    RS peerYes

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. Singapore SGIX Singapore, Singapore · PeeringDB 429
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 200G2 × 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).

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 APAC'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 2T across 3 exchanges.

Singapore DE-CIX ASEAN Singapore, Singapore 103.162.254.119
103.162.254.120
2001:df6:480::f23e:0:1
2001:df6:480::f23e:0:2
2 × 200G 16 routes Not in PeeringDB
Singapore Equinix Singapore Singapore, Singapore 27.111.229.210
27.111.230.113
2001:de8:4::6:2014:1
2001:de8:4::6:2014:2
2 × 600G Yes PeeringDB
Singapore SGIX Singapore, Singapore 103.16.102.92
103.16.102.233
2001:de8:12:100::92
2001:de8:12:100::233
2 × 200G Yes Both Speed differs

Telegram Messenger APAC lists no facilities in PeeringDB.