Observed topology
AS1403 EBOX
Residential ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS1403: 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 |
|---|---|---|---|---|
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 10,614 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 2,088 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 444 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 243 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 20 |
| AS22652 | Videotron Ltee | Residential | IPv6 | 20 |
| AS24482 | SG.GS | Hosting | IPv6 | 20 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv6 | 20 |
| AS6327 | Shaw Communications | Residential | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS1403 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 32,584 |
| AS6327 | Shaw Communications | Residential | IPv4 IPv6 | 7,936 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 6,882 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 4,778 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 2,610 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 2,152 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 1,412 |
| AS16276 | OVH SAS | Hosting | IPv4 IPv6 | 1,363 |
| AS19515 | Oricom Internet inc. | Unclassified | IPv4 IPv6 | 914 |
| AS36351 | IBM Cloud | Hosting | IPv4 IPv6 | 666 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1403 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 2,120,635 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 462,678 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 17,692 |
| AS32787 | Akamai Technologies, Inc. | Hosting | IPv4 IPv6 | 13,058 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 11,991 |
| AS6327 | Shaw Communications | Residential | IPv4 IPv6 | 10,940 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 10,704 |
| AS1828 | Unitas Global | Unclassified | IPv4 IPv6 | 4,428 |
| AS35280 | F5 Networks SARL | Hosting | IPv4 IPv6 | 3,770 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 3,387 |
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.