asn.dev

Observed topology

AS2 UDEL-DCN

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2: 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
AS45609Bharti Airtel Ltd. AS for GPRS ServiceMobileIPv4118
AS34University of DelawareUnclassifiedIPv463
AS41837"South telephone company" LLCUnclassifiedIPv458
AS203794LLC Gals-TelecomUnclassifiedIPv444
AS52752Vegas Telecom Informatica Ltda.UnclassifiedIPv49
AS270792luciano comin cardozo-meUnclassifiedIPv46
AS37628KAB TechnologiesUnclassifiedIPv42
AS199268LANCOM inzeniring racunalniskig sistemov d.o.o.UnclassifiedIPv61
AS327753SBM BANK (KENYA) LIMITEDUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37280Broad Based Communications LimitedHostingIPv42

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS45609Bharti Airtel Ltd. AS for GPRS ServiceMobileIPv4118
AS34University of DelawareUnclassifiedIPv463
AS41837"South telephone company" LLCUnclassifiedIPv458
AS203794LLC Gals-TelecomUnclassifiedIPv444
AS52752Vegas Telecom Informatica Ltda.UnclassifiedIPv49
AS270792luciano comin cardozo-meUnclassifiedIPv46
AS37280Broad Based Communications LimitedHostingIPv42
AS37613DOLPHIN TELECOMMUNICATION LIMITEDUnclassifiedIPv42
AS37628KAB TechnologiesUnclassifiedIPv42
AS199268LANCOM inzeniring racunalniskig sistemov d.o.o.UnclassifiedIPv61

Provenance

Where this comes from

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