asn.dev

Observed topology

AS37371 HORMUUD

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37371: 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
AS30990DJIBOUTI TELECOM S.A.UnclassifiedIPv41,521
AS37100SEACOM LimitedUnclassifiedIPv4500
AS174Cogent Communications, LLCTransitIPv4372
AS6939Hurricane Electric LLCTransitIPv477
AS328250Golis Telecom SomaliaUnclassifiedIPv458
AS328977Wavex Internet Service Provider LTDResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS327768Somcast Networks LLCUnclassifiedIPv4236
AS327764Somali Research & Education Network(SomaliREN)UnclassifiedIPv4232
AS329692HTG CLOUDS LIMITEDUnclassifiedIPv4118

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30990DJIBOUTI TELECOM S.A.UnclassifiedIPv41,539
AS174Cogent Communications, LLCTransitIPv4760
AS37100SEACOM LimitedUnclassifiedIPv4680
AS327768Somcast Networks LLCUnclassifiedIPv4236
AS327764Somali Research & Education Network(SomaliREN)UnclassifiedIPv4232
AS329692HTG CLOUDS LIMITEDUnclassifiedIPv4118
AS6939Hurricane Electric LLCTransitIPv477
AS328250Golis Telecom SomaliaUnclassifiedIPv458
AS328977Wavex Internet Service Provider LTDResidentialIPv43

Provenance

Where this comes from

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