asn.dev

Observed topology

AS211609 OKKO-AS OKKO LLC

Hosting RIPE

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS211609: 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
AS12389PJSC RostelecomResidentialIPv4625
AS31133PJSC MegaFonMobileIPv4250
AS31500Global Network Management IncUnclassifiedIPv4176
AS3216PJSC "Vimpelcom"MobileIPv4146
AS208677"Cloud Technologies" LLC trading as Cloud.ruUnclassifiedIPv4123
AS20485Joint Stock Company TransTeleComUnclassifiedIPv477
AS8359MTS PJSCMobileIPv432
AS57304JSC "RetnNet"UnclassifiedIPv422
AS51028Zummer LLCUnclassifiedIPv414
AS6939Hurricane Electric LLCTransitIPv413

All 22 upstreams →

Transit

Downstream networks

inferred

Networks for which AS211609 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 22

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4625
AS31133PJSC MegaFonMobileIPv4250
AS31500Global Network Management IncUnclassifiedIPv4176
AS3216PJSC "Vimpelcom"MobileIPv4146
AS208677"Cloud Technologies" LLC trading as Cloud.ruUnclassifiedIPv4123
AS20485Joint Stock Company TransTeleComUnclassifiedIPv477
AS8359MTS PJSCMobileIPv432
AS57304JSC "RetnNet"UnclassifiedIPv422
AS51028Zummer LLCUnclassifiedIPv414
AS6939Hurricane Electric LLCTransitIPv413

All 22 adjacent →

Provenance

Where this comes from

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