asn.dev

Observed topology

AS40703 WBD-AS40703

Unclassified ARIN

Upstreams 10 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 0
Upstream graph Who carries AS40703, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS40703 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS7018AT&T Enterprises, LLCResidentialIPv4120
AS5662Turner Broadcasting System, Inc.HostingIPv4119
AS6461Zayo BandwidthTransitIPv4110
AS13237euNetworks GmbHUnclassifiedIPv461
AS2686AT&T Enterprises, LLCUnclassifiedIPv460
AS8220COLT Technology Services Group LimitedHostingIPv458
AS2687AT&T Enterprises, LLCUnclassifiedIPv457
AS11014CPSResidentialIPv436
AS16814NSS S.A.UnclassifiedIPv427
AS2685AT&T Enterprises, LLCUnclassifiedIPv46

Transit

Downstream networks

inferred

Networks for which AS40703 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS11726WB Games Inc.UnclassifiedIPv459

Adjacency

Adjacent networks

All 11

Every AS seen directly next to AS40703 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS7018AT&T Enterprises, LLCResidentialIPv4179
AS5662Turner Broadcasting System, Inc.HostingIPv4119
AS6461Zayo BandwidthTransitIPv4110
AS13237euNetworks GmbHUnclassifiedIPv461
AS2686AT&T Enterprises, LLCUnclassifiedIPv460
AS11726WB Games Inc.UnclassifiedIPv459
AS8220COLT Technology Services Group LimitedHostingIPv458
AS2687AT&T Enterprises, LLCUnclassifiedIPv457
AS11014CPSResidentialIPv436
AS16814NSS S.A.UnclassifiedIPv427

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.