asn.dev

Observed topology

AS37305 FON

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37305: 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
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6668
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv6395
AS6939Hurricane Electric LLCTransitIPv4132
AS328977Wavex Internet Service Provider LTDResidentialIPv419

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37019INTERSAT AFRICA LTDUnclassifiedIPv42,009
AS329087Ace Micro Services LimitedUnclassifiedIPv4262
AS329002Pan African IX Data Centres Kenya LtdUnclassifiedIPv4100
AS329026Kenyaweb.com LimitedUnclassifiedIPv467
AS29032IDDQD-ASUnclassifiedIPv460
AS327732Dalkom SomaliaHostingIPv632
AS328162Icolo LtdUnclassifiedIPv45

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS37019INTERSAT AFRICA LTDUnclassifiedIPv42,009
AS37100SEACOM LimitedUnclassifiedIPv4 IPv61,828
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv61,716
AS329087Ace Micro Services LimitedUnclassifiedIPv4262
AS6939Hurricane Electric LLCTransitIPv4164
AS329002Pan African IX Data Centres Kenya LtdUnclassifiedIPv4100
AS329026Kenyaweb.com LimitedUnclassifiedIPv467
AS29032IDDQD-ASUnclassifiedIPv460
AS328977Wavex Internet Service Provider LTDResidentialIPv441
AS327732Dalkom SomaliaHostingIPv632

Provenance

Where this comes from

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