asn.dev

Observed topology

AS55081 24SHELLS - 24 SHELLS

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55081: 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
AS3257GTT Communications Inc.TransitIPv4 IPv6799
AS6939Hurricane Electric LLCTransitIPv490
AS9002RETN LimitedUnclassifiedIPv467
AS33891Core-Backbone GmbHHostingIPv411
AS24482SG.GSHostingIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59678SYSTEM36 LLCHostingIPv4 IPv6187
AS402517DataUnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv61,227
AS59678SYSTEM36 LLCHostingIPv4 IPv6362
AS402517DataUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv4108
AS9002RETN LimitedUnclassifiedIPv497
AS33891Core-Backbone GmbHHostingIPv413
AS24482SG.GSHostingIPv412

Provenance

Where this comes from

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