asn.dev

Observed topology

AS401066 OMNL-ASN-1

Unclassified ARIN Network Services

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS401066: 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
AS212895Johannes ErnstUnclassifiedIPv4 IPv667
AS6939Hurricane Electric LLCTransitIPv626
AS34927iFog GmbHHostingIPv625
AS5405Inter.link GmbHUnclassifiedIPv69
AS204092Association GRIFONUnclassifiedIPv61
AS215114Stevan Durand--L'Hours t/a SLBCLOUDUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS218500David TrolpUnclassifiedIPv429
AS215296Raoul Brouns is trading as LowPing NLUnclassifiedIPv418
AS218705Jeremy GumbleyUnclassifiedIPv63

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS212895Johannes ErnstUnclassifiedIPv4 IPv667
AS5405Inter.link GmbHUnclassifiedIPv4 IPv630
AS215114Stevan Durand--L'Hours t/a SLBCLOUDUnclassifiedIPv4 IPv630
AS218500David TrolpUnclassifiedIPv429
AS6939Hurricane Electric LLCTransitIPv626
AS34927iFog GmbHHostingIPv625
AS215296Raoul Brouns is trading as LowPing NLUnclassifiedIPv418
AS218705Jeremy GumbleyUnclassifiedIPv63
AS204092Association GRIFONUnclassifiedIPv61

Provenance

Where this comes from

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