asn.dev

Observed topology

AS208677 CLOUDRU-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208677: 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
AS43298Storm Networks LLCUnclassifiedIPv46,033
AS197068HLL LLCHostingIPv461
AS3216PJSC "Vimpelcom"MobileIPv460
AS57304JSC "RetnNet"UnclassifiedIPv453
AS8359MTS PJSCMobileIPv625
AS201706SERVICEPIPE LLCUnclassifiedIPv4 IPv616
AS9002RETN LimitedUnclassifiedIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS211609OKKO LLCHostingIPv4123
AS198255JSC SETTLEMENT SOLUTIONSUnclassifiedIPv461

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS43298Storm Networks LLCUnclassifiedIPv46,217
AS211609OKKO LLCHostingIPv4123
AS197068HLL LLCHostingIPv461
AS198255JSC SETTLEMENT SOLUTIONSUnclassifiedIPv461
AS3216PJSC "Vimpelcom"MobileIPv460
AS57304JSC "RetnNet"UnclassifiedIPv453
AS8359MTS PJSCMobileIPv625
AS201706SERVICEPIPE LLCUnclassifiedIPv4 IPv616
AS9002RETN LimitedUnclassifiedIPv47

Provenance

Where this comes from

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