asn.dev

Observed topology

AS34397 CYBERIA-RUH Middle East Internet Company Limited

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS34397: 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
AS39386Saudi Telecom Company JSCUnclassifiedIPv41,968
AS35753Etihad Salam Telecom CJSCUnclassifiedIPv41,056
AS35819Etihad Etisalat, a joint stock companyMobileIPv4509
AS32787Akamai Technologies, Inc.HostingIPv4118

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48937Saudi National Bank JSCUnclassifiedIPv4291
AS28938Sultan Bin Abdulaziz FoundationUnclassifiedIPv4171
AS60055Saudi Chevron Phillips LLCUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39386Saudi Telecom Company JSCUnclassifiedIPv42,240
AS35753Etihad Salam Telecom CJSCUnclassifiedIPv41,139
AS35819Etihad Etisalat, a joint stock companyMobileIPv4674
AS48937Saudi National Bank JSCUnclassifiedIPv4291
AS28938Sultan Bin Abdulaziz FoundationUnclassifiedIPv4171
AS32787Akamai Technologies, Inc.HostingIPv4118
AS60055Saudi Chevron Phillips LLCUnclassifiedIPv458

Provenance

Where this comes from

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