asn.dev

Observed topology

AS39444 OWENTIS-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39444: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6325
AS6461Zayo BandwidthTransitIPv4 IPv6126
AS30781Free Pro SASHostingIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv67
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv67
AS3215Orange S.A.MobileIPv46
AS37100SEACOM LimitedUnclassifiedIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS9002RETN LimitedUnclassifiedIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202604NG Cloud SASUnclassifiedIPv4 IPv679

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6388
AS6461Zayo BandwidthTransitIPv4 IPv6132
AS202604NG Cloud SASUnclassifiedIPv4 IPv679
AS30781Free Pro SASHostingIPv4 IPv670
AS24482SG.GSHostingIPv4 IPv68
AS37100SEACOM LimitedUnclassifiedIPv47
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv67
AS3215Orange S.A.MobileIPv46
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS9002RETN LimitedUnclassifiedIPv61

Provenance

Where this comes from

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