asn.dev

Observed topology

AS22702 RINGSQUARED - RingSquared

Residential ARIN Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22702: 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
AS11178AccessPlusUnclassifiedIPv42,230
AS701Verizon BusinessResidentialIPv4313
AS9002RETN LimitedUnclassifiedIPv417
AS3130RGnet OUUnclassifiedIPv415
AS24482SG.GSHostingIPv415
AS394256Tech Futures Interactive Inc.UnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv48
AS293ESnetUnclassifiedIPv41
AS7575Australian Academic and Research Network (AARNet)EducationIPv41
AS34927iFog GmbHHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396103WB Games Inc.UnclassifiedIPv46

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS11178AccessPlusUnclassifiedIPv42,236
AS701Verizon BusinessResidentialIPv4313
AS9002RETN LimitedUnclassifiedIPv417
AS3130RGnet OUUnclassifiedIPv415
AS24482SG.GSHostingIPv415
AS394256Tech Futures Interactive Inc.UnclassifiedIPv415
AS6939Hurricane Electric LLCTransitIPv48
AS396103WB Games Inc.UnclassifiedIPv46
AS293ESnetUnclassifiedIPv41
AS7575Australian Academic and Research Network (AARNet)EducationIPv41

All 11 adjacent →

Provenance

Where this comes from

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