Observed topology
AS40703 WBD-AS40703
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS40703: 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 |
|---|---|---|---|---|
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 | 120 |
| AS5662 | Turner Broadcasting System, Inc. | Hosting | IPv4 | 119 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 110 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 | 61 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 60 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 58 |
| AS2687 | AT&T Enterprises, LLC | Unclassified | IPv4 | 57 |
| AS11014 | CPS | Residential | IPv4 | 36 |
| AS16814 | NSS S.A. | Unclassified | IPv4 | 27 |
| AS2685 | AT&T Enterprises, LLC | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS40703 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11726 | WB Games Inc. | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS40703 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 | 179 |
| AS5662 | Turner Broadcasting System, Inc. | Hosting | IPv4 | 119 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 | 110 |
| AS13237 | euNetworks GmbH | Unclassified | IPv4 | 61 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 60 |
| AS11726 | WB Games Inc. | Unclassified | IPv4 | 59 |
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 | 58 |
| AS2687 | AT&T Enterprises, LLC | Unclassified | IPv4 | 57 |
| AS11014 | CPS | Residential | IPv4 | 36 |
| AS16814 | NSS S.A. | Unclassified | IPv4 | 27 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.