Observed topology
AS5690 VIANET INC 5690 - Vianet Inc.
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS5690: 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.
Transit
Downstream networks
Networks for which AS5690 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS14673 | FiberSpeed | Unclassified | IPv4 | 316 |
| AS22060 | Netspectrum Wireless Internet Solutions | Unclassified | IPv4 | 295 |
| AS19595 | Sudbury & District Health Unit | Unclassified | IPv4 | 135 |
| AS22494 | 7098693 Canada Inc. | Unclassified | IPv4 | 118 |
| AS400938 | Highlands Internet Services Ltd. | Unclassified | IPv4 | 118 |
| AS17042 | Conseil scolaire de district catholique Franco-Nord | Unclassified | IPv4 | 59 |
| AS32756 | Cambrian College of Applied Arts & Technology | Unclassified | IPv4 | 54 |
| AS54351 | Communicate Freely | Unclassified | IPv4 IPv6 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5690 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,380 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 2,264 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 950 |
| AS14673 | FiberSpeed | Unclassified | IPv4 | 316 |
| AS22060 | Netspectrum Wireless Internet Solutions | Unclassified | IPv4 | 295 |
| AS22652 | Videotron Ltee | Residential | IPv4 | 202 |
| AS19595 | Sudbury & District Health Unit | Unclassified | IPv4 | 135 |
| AS22494 | 7098693 Canada Inc. | Unclassified | IPv4 | 118 |
| AS400938 | Highlands Internet Services Ltd. | Unclassified | IPv4 | 118 |
| AS24482 | SG.GS | Hosting | IPv4 | 101 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.