asn.dev

Observed topology

AS22772 LOGIN

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS22772: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6735
AS6461Zayo BandwidthTransitIPv4 IPv6261
AS24482SG.GSHostingIPv4 IPv68
AS53767iCastCenterHostingIPv48
AS17639Converge ICT Solutions Inc.UnclassifiedIPv47
AS22773Cox Communications Inc.ResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32506Experior Networks LLCUnclassifiedIPv4336
AS6491TeleKachinaUnclassifiedIPv4 IPv6166
AS398407Intelium Corp.UnclassifiedIPv465

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv61,191
AS6461Zayo BandwidthTransitIPv4 IPv6346
AS32506Experior Networks LLCUnclassifiedIPv4336
AS6491TeleKachinaUnclassifiedIPv4 IPv6166
AS398407Intelium Corp.UnclassifiedIPv465
AS24482SG.GSHostingIPv4 IPv617
AS53767iCastCenterHostingIPv417
AS17639Converge ICT Solutions Inc.UnclassifiedIPv415
AS22773Cox Communications Inc.ResidentialIPv42

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.