asn.dev

Observed topology

AS22653 GLOBALCOMPASS - Cyber Wurx LLC

Hosting ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22653: 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
AS19531Nodes DirectHostingIPv4 IPv6723
AS6939Hurricane Electric LLCTransitIPv4157
AS2914NTT America, Inc.TransitIPv4 IPv625

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7489HostUSHostingIPv4 IPv6144
AS41564Orion Network LimitedHostingIPv4112
AS141518SUBHOSTING INNOVATIONS PRIVATE LIMITEDUnclassifiedIPv410
AS63119Angelnet LimitedUnclassifiedIPv42

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS19531Nodes DirectHostingIPv4 IPv66,164
AS41564Orion Network LimitedHostingIPv45,288
AS6939Hurricane Electric LLCTransitIPv4157
AS7489HostUSHostingIPv4 IPv6144
AS2914NTT America, Inc.TransitIPv4 IPv628
AS141518SUBHOSTING INNOVATIONS PRIVATE LIMITEDUnclassifiedIPv410
AS63119Angelnet LimitedUnclassifiedIPv42

Provenance

Where this comes from

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