Observed topology
AS819 LARG-NET - LARG*net London and Region Global Computer Network
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS819: 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 |
|---|---|---|---|---|
| AS19752 | Hydro One Telecom Inc. | Unclassified | IPv4 | 542 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 439 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 60 |
| AS26677 | ORION | Unclassified | IPv4 | 60 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 43 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 10 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 9 |
| AS1403 | EBOX | Residential | IPv6 | 2 |
Transit
Downstream networks
Networks for which AS819 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS823 | University of Western Ontario | Unclassified | IPv4 IPv6 | 916 |
| AS822 | St. Joseph's Health Care, London | Unclassified | IPv4 | 326 |
| AS397264 | City of London | Unclassified | IPv4 IPv6 | 84 |
| AS394554 | Woodstock General Hospital | Unclassified | IPv4 | 66 |
| AS395235 | St. Thomas-Elgin General Hospital | Unclassified | IPv4 | 66 |
| AS14933 | London Hydro | Unclassified | IPv4 | 33 |
Adjacency
Adjacent networks
Every AS seen directly next to AS819 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,260 |
| AS823 | University of Western Ontario | Unclassified | IPv4 IPv6 | 916 |
| AS19752 | Hydro One Telecom Inc. | Unclassified | IPv4 | 571 |
| AS26677 | ORION | Unclassified | IPv4 | 425 |
| AS822 | St. Joseph's Health Care, London | Unclassified | IPv4 | 326 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 168 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 122 |
| AS397264 | City of London | Unclassified | IPv4 IPv6 | 84 |
| AS394554 | Woodstock General Hospital | Unclassified | IPv4 | 66 |
| AS395235 | St. Thomas-Elgin General Hospital | Unclassified | IPv4 | 66 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-02 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.44M 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.