asn.dev

Observed topology

AS1011 ACCUTAR-NA-01

Unclassified ARIN

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS1011: 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
AS46450Pilot Fiber, Inc.ResidentialIPv4 IPv689
AS20119Arrow Group Inc.UnclassifiedIPv4 IPv686
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS9002RETN LimitedUnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv63
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv63
AS398465Rackdog, LLCResidentialIPv43
AS293ESnetUnclassifiedIPv42
AS3130RGnet OUUnclassifiedIPv42
AS7575Australian Academic and Research Network (AARNet)EducationIPv42

Transit

Downstream networks

inferred

Networks for which AS1011 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 11

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

ASNetworkTypeFamiliesPaths seen
AS46450Pilot Fiber, Inc.ResidentialIPv4 IPv689
AS20119Arrow Group Inc.UnclassifiedIPv4 IPv686
AS6939Hurricane Electric LLCTransitIPv4 IPv649
AS9002RETN LimitedUnclassifiedIPv44
AS24482SG.GSHostingIPv4 IPv63
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv63
AS398465Rackdog, LLCResidentialIPv43
AS293ESnetUnclassifiedIPv42
AS3130RGnet OUUnclassifiedIPv42
AS7575Australian Academic and Research Network (AARNet)EducationIPv42

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.