asn.dev

Observed topology

AS22283 SIDLEY

Unclassified ARIN

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS22283: 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
AS7018AT&T Enterprises, LLCResidentialIPv4348
AS701Verizon BusinessResidentialIPv4322
AS6461Zayo BandwidthTransitIPv4234
AS2914NTT America, Inc.TransitIPv4169
AS2686AT&T Enterprises, LLCUnclassifiedIPv477
AS703Verizon BusinessUnclassifiedIPv465
AS702Verizon BusinessUnclassifiedIPv458
AS8220COLT Technology Services Group LimitedHostingIPv444
AS3561CenturyLink Communications, LLCHostingIPv428
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv426

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS22283 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 AS22283 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS7018AT&T Enterprises, LLCResidentialIPv4348
AS701Verizon BusinessResidentialIPv4322
AS6461Zayo BandwidthTransitIPv4234
AS2914NTT America, Inc.TransitIPv4169
AS2686AT&T Enterprises, LLCUnclassifiedIPv477
AS703Verizon BusinessUnclassifiedIPv465
AS702Verizon BusinessUnclassifiedIPv458
AS8220COLT Technology Services Group LimitedHostingIPv444
AS3561CenturyLink Communications, LLCHostingIPv428
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv426

All 13 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.