asn.dev

Observed topology

AS2631 WBD-AS2631 - Discovery Communications

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2631: 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
AS6461Zayo BandwidthTransitIPv4794
AS3356Level 3 Parent, LLCTransitIPv4250
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4118
AS2687AT&T Enterprises, LLCUnclassifiedIPv4112
AS13237euNetworks GmbHUnclassifiedIPv466
AS4230CLARO S.A.ResidentialIPv458
AS8151UNINETMobileIPv458
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv457
AS5555Sohonet LimitedUnclassifiedIPv452
AS29838Atlantic Metro Communications II, Inc.HostingIPv48

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4794
AS3356Level 3 Parent, LLCTransitIPv4250
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4118
AS2687AT&T Enterprises, LLCUnclassifiedIPv4112
AS13237euNetworks GmbHUnclassifiedIPv466
AS4230CLARO S.A.ResidentialIPv458
AS8151UNINETMobileIPv458
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv457
AS5555Sohonet LimitedUnclassifiedIPv452
AS29838Atlantic Metro Communications II, Inc.HostingIPv48

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.