asn.dev

Observed topology

AS205111 ZOHO-EU

Unclassified RIPE

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

Transit

Upstream networks

All 23

Networks observed carrying traffic for AS205111: 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
AS6461Zayo BandwidthTransitIPv4675
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4424
AS35819Etihad Etisalat, a joint stock companyMobileIPv4327
AS1299Arelion Sweden ABTransitIPv4304
AS198949Radware LtdUnclassifiedIPv4162
AS174Cogent Communications, LLCTransitIPv4160
AS42156GNX B.V.UnclassifiedIPv466
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv455
AS35753Etihad Salam Telecom CJSCUnclassifiedIPv427
AS6939Hurricane Electric LLCTransitIPv48

All 23 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS397849ZOHOHostingIPv4 IPv636

Adjacency

Adjacent networks

All 24

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4675
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6443
AS35819Etihad Etisalat, a joint stock companyMobileIPv4327
AS1299Arelion Sweden ABTransitIPv4304
AS198949Radware LtdUnclassifiedIPv4162
AS174Cogent Communications, LLCTransitIPv4160
AS42156GNX B.V.UnclassifiedIPv474
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv664
AS397849ZOHOHostingIPv4 IPv636
AS35753Etihad Salam Telecom CJSCUnclassifiedIPv427

All 24 adjacent →

Provenance

Where this comes from

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