asn.dev

Observed topology

AS40092 ONIAAS - HostPapa

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40092: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6514
AS6461Zayo BandwidthTransitIPv4 IPv6408
AS3356Level 3 Parent, LLCTransitIPv4 IPv6288
AS36352HostPapaHostingIPv4 IPv6259

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36352HostPapaHostingIPv4 IPv61,675
AS30447Internet Names For Business Inc.HostingIPv4 IPv6924
AS14116Internet Names For Business Inc.HostingIPv4313
AS9115Hostpapa UK Ltd.HostingIPv4 IPv6252

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS36352HostPapaHostingIPv4 IPv62,255
AS174Cogent Communications, LLCTransitIPv4 IPv62,239
AS6461Zayo BandwidthTransitIPv4 IPv61,667
AS30447Internet Names For Business Inc.HostingIPv4 IPv6924
AS3356Level 3 Parent, LLCTransitIPv4 IPv6789
AS14116Internet Names For Business Inc.HostingIPv4313
AS9115Hostpapa UK Ltd.HostingIPv4 IPv6252

Provenance

Where this comes from

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