asn.dev

Observed topology

AS49362 DSV

Unclassified ARIN

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS49362: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6935
AS16637MTN SAMobileIPv4150
AS3356Level 3 Parent, LLCTransitIPv4 IPv6134
AS174Cogent Communications, LLCTransitIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv627
AS7473Singapore Telecommunications LtdUnclassifiedIPv414
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv48
AS7018AT&T Enterprises, LLCResidentialIPv48
AS24482SG.GSHostingIPv4 IPv66

All 18 upstreams →

Transit

Downstream networks

inferred

Networks for which AS49362 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

All 18

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6935
AS16637MTN SAMobileIPv4150
AS3356Level 3 Parent, LLCTransitIPv4 IPv6134
AS174Cogent Communications, LLCTransitIPv4 IPv6104
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS31027GlobalConnect A/SUnclassifiedIPv4 IPv627
AS7473Singapore Telecommunications LtdUnclassifiedIPv414
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv48
AS7018AT&T Enterprises, LLCResidentialIPv48
AS24482SG.GSHostingIPv4 IPv66

All 18 adjacent →

Provenance

Where this comes from

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