asn.dev

Observed topology

AS59588 ZAINAS-

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59588: 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
AS203217Horizon Scope Mobile Telecom WLLUnclassifiedIPv4 IPv65,092
AS39216Pulk Company for General Trading, Communications & Investment, Ltd.UnclassifiedIPv4 IPv6150
AS21277Allay Nawroz Telecom Company for Communication/Ltd.UnclassifiedIPv4117
AS212330Civilisation Information Technology, communication and internet services Co., LTDUnclassifiedIPv459

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS203217Horizon Scope Mobile Telecom WLLUnclassifiedIPv4 IPv65,185
AS39216Pulk Company for General Trading, Communications & Investment, Ltd.UnclassifiedIPv4 IPv6150
AS21277Allay Nawroz Telecom Company for Communication/Ltd.UnclassifiedIPv4117
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv693
AS212330Civilisation Information Technology, communication and internet services Co., LTDUnclassifiedIPv459

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.