asn.dev

Observed topology

AS199669 ATLEX-AS

Hosting ARIN

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS199669: 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
AS31500Global Network Management IncUnclassifiedIPv4 IPv6233
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6154
AS29076Citytelecom LLCHostingIPv4 IPv6114
AS6939Hurricane Electric LLCTransitIPv4 IPv6102
AS199599Telecom-Birzha, LLCUnclassifiedIPv465
AS51248Host-Telecom.com s.r.o.HostingIPv459
AS9002RETN LimitedUnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS56655Gigahost ASUnclassifiedIPv4 IPv612

All 15 upstreams →

Transit

Downstream networks

inferred

Networks for which AS199669 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 15

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv4 IPv6233
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6154
AS29076Citytelecom LLCHostingIPv4 IPv6114
AS6939Hurricane Electric LLCTransitIPv4 IPv6102
AS199599Telecom-Birzha, LLCUnclassifiedIPv465
AS51248Host-Telecom.com s.r.o.HostingIPv459
AS9002RETN LimitedUnclassifiedIPv4 IPv615
AS24482SG.GSHostingIPv4 IPv615
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv613
AS56655Gigahost ASUnclassifiedIPv4 IPv612

All 15 adjacent →

Provenance

Where this comes from

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