asn.dev

Observed topology

AS37002 Reunicable

Unclassified AFRINIC

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

Transit

Upstream networks

All 19

Networks observed carrying traffic for AS37002: 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
AS174Cogent Communications, LLCTransitIPv4 IPv6709
AS1273IDDQD-ASBusinessIPv4 IPv6565
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6545
AS6939Hurricane Electric LLCTransitIPv4347
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv6226
AS37721Virtual Technologies & SolutionsResidentialIPv447
AS3741Dimension DataUnclassifiedIPv446
AS24482SG.GSHostingIPv4 IPv646
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv646
AS12779IT.Gate S.p.A.UnclassifiedIPv445

All 19 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv694

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6732
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6576
AS1273IDDQD-ASBusinessIPv4 IPv6565
AS6939Hurricane Electric LLCTransitIPv4 IPv6367
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv6226
AS14789Cloudflare, Inc.UnclassifiedIPv4 IPv694
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv649
AS24482SG.GSHostingIPv4 IPv648
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv648
AS3741Dimension DataUnclassifiedIPv447

All 21 adjacent →

Provenance

Where this comes from

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