asn.dev

Observed topology

AS203391 CLOUDNSNET Cloud DNS Ltd

Hosting RIPE Content

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

Transit

Upstream networks

All 25

Networks observed carrying traffic for AS203391: 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
AS60068Datacamp LimitedHostingIPv4 IPv6154
AS25369Hydra Communications LtdHostingIPv4 IPv6110
AS20473The Constant Company, LLCHostingIPv4 IPv664
AS63023GTHostHostingIPv438
AS38001NewMedia Express Pte LtdHostingIPv4 IPv630
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv628
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv628
AS56655Gigahost ASUnclassifiedIPv4 IPv626
AS40994Hohl IT e.U.HostingIPv4 IPv616
AS54527Astute InternetHostingIPv4 IPv616

All 25 upstreams →

Transit

Downstream networks

inferred

Networks for which AS203391 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 25

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv6154
AS25369Hydra Communications LtdHostingIPv4 IPv6110
AS20473The Constant Company, LLCHostingIPv4 IPv664
AS63023GTHostHostingIPv438
AS38001NewMedia Express Pte LtdHostingIPv4 IPv630
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv628
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv628
AS56655Gigahost ASUnclassifiedIPv4 IPv626
AS40994Hohl IT e.U.HostingIPv4 IPv616
AS54527Astute InternetHostingIPv4 IPv616

All 25 adjacent →

Provenance

Where this comes from

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