China Telecom / CN2
AS4809
China Telecom
Tools: Where can I peer with China Telecom / CN2? · Where should China Telecom / CN2 peer next? · Compare China Telecom / CN2 with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
10 things to fix in China Telecom / CN2's PeeringDB record, from what its exchanges publish: 9 to add, 1 to correct. As of 2026-11-19 12:40 UTC.
Make the changes on China Telecom / CN2'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 (9)
On the exchange's own member list, but not in China Telecom / CN2's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 196.216.148.59 IPv6 – Speed 1000 Mbps (1G) RS peer Yes -
IPv4 196.223.21.70 IPv6 2001:43f8:60:1::70 Speed 1000 Mbps (1G) RS peer No -
NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592From its IX-F export and website members list
IPv4 196.60.9.11 IPv6 2001:43f8:6d0::4809 Speed 10000 Mbps (10G) 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.
-
IPv4 185.1.8.76 IPv6 2001:7f8:73::12c9:0:1 Speed 1000 Mbps (1G) 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 IPv6 address missing from PeeringDB none 2001:de8:12:100::53 Port speed differs 10G 20G - In the entry with IPv4 103.16.102.53: set IPv6 to 2001:de8:12:100::53 (now empty); set Speed to 20000 (20G) (now 10000).
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 11 |
| Nov 18, 2026 | 11 |
| Nov 17, 2026 | 11 |
| Nov 16, 2026 | 11 |
| Nov 15, 2026 | 11 |
| Nov 14, 2026 | 11 |
| Nov 13, 2026 | 11 |
| Nov 12, 2026 | 11 |
| Nov 11, 2026 | 11 |
| Nov 10, 2026 | 11 |
| Nov 9, 2026 | 11 |
| Nov 8, 2026 | 11 |
| Nov 7, 2026 | 11 |
| Nov 6, 2026 | 11 |
| Nov 5, 2026 | 11 |
| Nov 4, 2026 | 11 |
| Nov 3, 2026 | 11 |
| Nov 2, 2026 | 11 |
| Nov 1, 2026 | 11 |
| Oct 31, 2026 | 11 |
| Oct 30, 2026 | 11 |
| Oct 29, 2026 | 11 |
| Oct 28, 2026 | 11 |
| Oct 27, 2026 | 11 |
| Oct 26, 2026 | 11 |
| Oct 25, 2026 | 10 |
| Oct 24, 2026 | 10 |
| Oct 23, 2026 | 10 |
| Oct 22, 2026 | 11 |
| Oct 21, 2026 | 11 |
| Oct 20, 2026 | 11 |
| Oct 19, 2026 | 10 |
| Oct 18, 2026 | 11 |
| Oct 17, 2026 | 11 |
| Oct 16, 2026 | 11 |
| Oct 15, 2026 | 11 |
| Oct 14, 2026 | 11 |
| Oct 13, 2026 | 11 |
| Oct 12, 2026 | 11 |
| Oct 11, 2026 | 11 |
| Oct 10, 2026 | 11 |
| Oct 9, 2026 | 11 |
| Oct 8, 2026 | 11 |
| Oct 7, 2026 | 11 |
| Oct 6, 2026 | 11 |
| Oct 5, 2026 | 11 |
| Oct 4, 2026 | 11 |
| Oct 3, 2026 | 11 |
Map
Where China Telecom / CN2'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.
| Any2West Los Angeles and Silicon Valley, United States | 10G | PeeringDB | |
| GIXA Accra, Ghana | Not in PeeringDB | ||
| IX.br (PTT.br) Campinas Campinas/SP, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Curitiba Curitiba, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) Rio de Janeiro Rio de Janeiro/RJ, Brazil | Not in PeeringDB | ||
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | Not in PeeringDB | ||
| IXPN Lagos Lagos, Nigeria | 1G | Not in PeeringDB | |
| KIXP - Nairobi Nairobi, Kenya | 1G | Not in PeeringDB | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 10G | Not in PeeringDB | |
| SGIX Singapore, Singapore | 10G | Both IPv6 not in PeeringDBSpeed differs | |
| UAE-IX Dubai, United Arab Emirates | 1G | Not in PeeringDB |
These exchanges have a switch in a facility where China Telecom / CN2 lists itself in PeeringDB, but don't have China Telecom / CN2 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.
| HKIXHong Kong, Hong Kong | 300 | |
| JINXJohannesburg, South Africa | 215 | |
| NetIXSofia, Bulgaria | 204 | |
| Equinix São PauloSão Paulo, Brazil | 163 | |
| BBIX Hong KongHong Kong, Hong Kong | 104 | |
| LINX NairobiNairobi, Kenya | 70 | |
| SH-IXFujairah, United Arab Emirates | 43 | |
| NAPAfrica MAPS JohannesburgJohannesburg, South Africa | 31 | |
| IAIXHong Kong, Hong Kong | 20 | |
| Global Peer ExchangeWashington, United States | 6 | |
| JINX VoiceJohannesburg, South Africa | 4 |
Facilities (5)
The buildings China Telecom / CN2 lists in PeeringDB, and how many of the exchanges in each it's on.
| Teraco Johannesburg Campus, South AfricaJohannesburg | 1 of 6 | |
| Equinix SP2 - São PauloBarueri | 1 of 4 | |
| MEGA-i (iAdvantage Hong Kong)Hong Kong | 0 of 4 | |
| Africa Data Centres, Nairobi NBO1, KenyaNairobi | 1 of 2 | |
| SmartHub FujairahFujairah | 0 of 2 |