asn.dev

Observed topology

AS201661 ASN-AJC

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201661: 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
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4348
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv662
AS24482SG.GSHostingIPv4 IPv67
AS5617Orange Polska Spolka AkcyjnaMobileIPv46
AS20473The Constant Company, LLCHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS204905Prosperplast 1 Spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464
AS205075Prosperplast 1 Spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29535Orange Polska Spolka AkcyjnaUnclassifiedIPv4466
AS62081Stowarzyszenie e-PoludnieUnclassifiedIPv4 IPv668
AS204905Prosperplast 1 Spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464
AS205075Prosperplast 1 Spolka z ograniczona odpowiedzialnosciaUnclassifiedIPv464
AS24482SG.GSHostingIPv4 IPv69
AS5617Orange Polska Spolka AkcyjnaMobileIPv48
AS20473The Constant Company, LLCHostingIPv61

Provenance

Where this comes from

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