Observed topology
AS9814 FIBRLINK Beijing FibrLINK Networks Co.,Ltd.
Unclassified APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS9814: 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 |
|---|---|---|---|---|
| AS4847 | China Networks Inter-Exchange | Unclassified | IPv4 | 4,788 |
| AS141174 | INTELLIGENT CONNECTION LIMITED | Unclassified | IPv4 | 126 |
| AS4808 | China Unicom Beijing Province Network | Residential | IPv4 | 111 |
| AS23724 | IDC, China Telecommunications Corporation | Unclassified | IPv4 | 80 |
| AS56048 | China Mobile Communicaitons Corporation | Unclassified | IPv4 | 11 |
Transit
Downstream networks
Networks for which AS9814 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS18241 | State Power Information Net | Unclassified | IPv4 | 202 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9814 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS4847 | China Networks Inter-Exchange | Unclassified | IPv4 | 4,788 |
| AS141174 | INTELLIGENT CONNECTION LIMITED | Unclassified | IPv4 | 323 |
| AS18241 | State Power Information Net | Unclassified | IPv4 | 202 |
| AS4808 | China Unicom Beijing Province Network | Residential | IPv4 | 111 |
| AS23724 | IDC, China Telecommunications Corporation | Unclassified | IPv4 | 85 |
| AS56048 | China Mobile Communicaitons Corporation | Unclassified | IPv4 | 11 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.