Observed topology
AS4809 CHINATELECOM-CORE-WAN-CN2 - China Telecom Next Generation Carrier Network
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS4809: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 8,535 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,155 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,300 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,393 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 IPv6 | 1,202 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,009 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 635 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 611 |
| AS812 | Rogers Communications Canada Inc. | Mobile | IPv4 IPv6 | 571 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 271 |
Transit
Downstream networks
Networks for which AS4809 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4812 | China Telecom (Group) | Residential | IPv4 IPv6 | 7,354 |
| AS58777 | ChinaTelecom Cybersecurity Tech | Unclassified | IPv4 | 1,399 |
| AS4847 | China Networks Inter-Exchange | Unclassified | IPv4 IPv6 | 885 |
| AS136167 | CHINA TELECOM (MACAU) COMPANY LIMITED | Unclassified | IPv4 IPv6 | 626 |
| AS54600 | PEG TECH INC | Hosting | IPv4 | 324 |
| AS40065 | CNSERVERS LLC | Hosting | IPv4 | 268 |
| AS58518 | China Telecom | Unclassified | IPv4 | 238 |
| AS328543 | Sun Network Company Limited | Unclassified | IPv4 IPv6 | 233 |
| AS136198 | CHINANET Guangdong province Yuexi MAN network | Unclassified | IPv4 IPv6 | 217 |
| AS58517 | China Telecom | Unclassified | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS4809 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS23764 | CTGNet | Unclassified | IPv4 IPv6 | 18,363 |
| AS4812 | China Telecom (Group) | Residential | IPv4 IPv6 | 7,354 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 4,848 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,964 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,751 |
| AS54600 | PEG TECH INC | Hosting | IPv4 | 1,624 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 1,551 |
| AS58777 | ChinaTelecom Cybersecurity Tech | Unclassified | IPv4 | 1,399 |
| AS9304 | HGC Global Communications Limited | Hosting | IPv4 IPv6 | 1,374 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,373 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.