asn.dev

Observed topology

AS20454 SSASN2

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20454: 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
AS12189PhoenixNAP LLCHostingIPv4 IPv69,498

Transit

Downstream networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS398019Dynu Systems IncorporatedUnclassifiedIPv4 IPv61,716
AS22612Namecheap, Inc.HostingIPv4752
AS10489Armour Cloud, LLCHostingIPv4472
AS13480Ongoing Operations, LLCUnclassifiedIPv4177
AS32647Crucial Web Hosting, Ltd.HostingIPv4152
AS13816Vigilant TechnologiesUnclassifiedIPv4118
AS14939THRESHOLD COMMUNICATIONS,INC.ResidentialIPv4 IPv664
AS12259EBOCOM LLCUnclassifiedIPv460
AS11687City of Hope Medical CenterUnclassifiedIPv459
AS29833MEDICAL INFORMATICS ENGINEERINGUnclassifiedIPv459

All 20 downstreams →

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS12189PhoenixNAP LLCHostingIPv4 IPv613,444
AS398019Dynu Systems IncorporatedUnclassifiedIPv4 IPv61,716
AS22612Namecheap, Inc.HostingIPv4752
AS10489Armour Cloud, LLCHostingIPv4472
AS13480Ongoing Operations, LLCUnclassifiedIPv4177
AS32647Crucial Web Hosting, Ltd.HostingIPv4152
AS13816Vigilant TechnologiesUnclassifiedIPv4118
AS14939THRESHOLD COMMUNICATIONS,INC.ResidentialIPv4 IPv664
AS12259EBOCOM LLCUnclassifiedIPv460
AS11687City of Hope Medical CenterUnclassifiedIPv459

All 21 adjacent →

Provenance

Where this comes from

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