Observed topology
AS7311 FRONTIER
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS7311: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,655 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,192 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 294 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 179 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 88 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 88 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 74 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 | 27 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 19 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 | 18 |
Transit
Downstream networks
Networks for which AS7311 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS17266 | AllCore Communications Inc. | Unclassified | IPv4 | 1,363 |
| AS16949 | Edaptivity.com Inc | Unclassified | IPv4 | 520 |
| AS36472 | PALOMINO SYSTEM INNOVATIONS INC. | Hosting | IPv4 | 484 |
| AS13846 | Lavalife Corp. | Unclassified | IPv4 | 260 |
| AS33044 | Megawire Inc. | Unclassified | IPv4 | 252 |
| AS1070 | Peel Regional Police | Unclassified | IPv4 | 207 |
| AS394840 | Decisive Group inc. | Unclassified | IPv4 | 200 |
| AS30528 | E. I. Catalyst | Residential | IPv4 IPv6 | 177 |
| AS14673 | FiberSpeed | Unclassified | IPv4 | 156 |
| AS399743 | RuralLynx Inc | Unclassified | IPv4 | 141 |
Adjacency
Adjacent networks
Every AS seen directly next to AS7311 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 7,808 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 2,036 |
| AS17266 | AllCore Communications Inc. | Unclassified | IPv4 | 1,363 |
| AS16949 | Edaptivity.com Inc | Unclassified | IPv4 | 520 |
| AS36472 | PALOMINO SYSTEM INNOVATIONS INC. | Hosting | IPv4 | 484 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 356 |
| AS33044 | Megawire Inc. | Unclassified | IPv4 | 323 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 278 |
| AS13846 | Lavalife Corp. | Unclassified | IPv4 | 260 |
| AS1070 | Peel Regional Police | Unclassified | IPv4 | 207 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.