asn.dev

Observed topology

AS22612 NAMECHEAP-NET

Hosting ARIN

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS22612: 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
AS19551Incapsula IncHostingIPv413,838
AS174Cogent Communications, LLCTransitIPv4 IPv61,660
AS11855Unitas GlobalUnclassifiedIPv41,625
AS3257GTT Communications Inc.TransitIPv4 IPv6894
AS20454SECURED SERVERS LLCHostingIPv4767
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6335
AS6939Hurricane Electric LLCTransitIPv4 IPv6271
AS60558PHOENIX NAP, LLC.UnclassifiedIPv4120
AS19437SECURED SERVERS LLCHostingIPv459
AS20473The Constant Company, LLCHostingIPv459

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS22612 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 13

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

ASNetworkTypeFamiliesPaths seen
AS19551Incapsula IncHostingIPv413,838
AS174Cogent Communications, LLCTransitIPv4 IPv61,660
AS11855Unitas GlobalUnclassifiedIPv41,625
AS3257GTT Communications Inc.TransitIPv4 IPv6894
AS20454SECURED SERVERS LLCHostingIPv4767
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6335
AS6939Hurricane Electric LLCTransitIPv4 IPv6271
AS60558PHOENIX NAP, LLC.UnclassifiedIPv4120
AS19437SECURED SERVERS LLCHostingIPv459
AS20473The Constant Company, LLCHostingIPv459

All 13 adjacent →

Provenance

Where this comes from

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