asn.dev

Observed topology

AS208393 DEDCLOUD

Hosting RIPE

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS208393: 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
AS20473The Constant Company, LLCHostingIPv4 IPv699
AS917Misaka Network, Inc.UnclassifiedIPv45
AS35487Misaka Network, Inc.UnclassifiedIPv45
AS23961Misaka Network, Inc.UnclassifiedIPv43
AS56630Melbikomas UABHostingIPv42
AS56662Marcin GondekUnclassifiedIPv62
AS58313Misaka Network, Inc.UnclassifiedIPv42
AS63473HostHatch, LLCUnclassifiedIPv42
AS202297Skylon Solutions LimitedUnclassifiedIPv42
AS57494Adman LLCUnclassifiedIPv41

All 12 upstreams →

Transit

Downstream networks

inferred

Networks for which AS208393 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 12

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

ASNetworkTypeFamiliesPaths seen
AS20473The Constant Company, LLCHostingIPv4 IPv699
AS917Misaka Network, Inc.UnclassifiedIPv45
AS35487Misaka Network, Inc.UnclassifiedIPv45
AS23961Misaka Network, Inc.UnclassifiedIPv43
AS56630Melbikomas UABHostingIPv42
AS56662Marcin GondekUnclassifiedIPv62
AS58313Misaka Network, Inc.UnclassifiedIPv42
AS63473HostHatch, LLCUnclassifiedIPv42
AS202297Skylon Solutions LimitedUnclassifiedIPv42
AS57494Adman LLCUnclassifiedIPv41

All 12 adjacent →

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.