asn.dev

Observed topology

AS208349 O2CLOUD

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS208349: 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 RostelecomResidentialIPv4 IPv6521
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6217
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6150
AS31133PJSC MegaFonMobileIPv4 IPv6139
AS59796StormWall s.r.o.UnclassifiedIPv444
AS43298Storm Networks LLCUnclassifiedIPv416
AS24482SG.GSHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47440BUSINESS SYSTEM TELEHOUSE, OOOUnclassifiedIPv4 IPv6904
AS206904LLC "Citilink"UnclassifiedIPv4 IPv6206
AS47429OOO TABLOGIXUnclassifiedIPv462
AS206301LLC IT ExpertUnclassifiedIPv462
AS41667Ltd TAMI & CoUnclassifiedIPv436

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4 IPv61,341
AS47440BUSINESS SYSTEM TELEHOUSE, OOOUnclassifiedIPv4 IPv61,200
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6525
AS31133PJSC MegaFonMobileIPv4 IPv6365
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv6343
AS206904LLC "Citilink"UnclassifiedIPv4 IPv6206
AS47429OOO TABLOGIXUnclassifiedIPv462
AS206301LLC IT ExpertUnclassifiedIPv462
AS59796StormWall s.r.o.UnclassifiedIPv444
AS41667Ltd TAMI & CoUnclassifiedIPv436

All 13 adjacent →

Provenance

Where this comes from

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