asn.dev

Observed topology

AS329538 SOMTEL-K-LIMITED

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329538: 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 IPv687
AS30990DJIBOUTI TELECOM S.A.UnclassifiedIPv4 IPv663
AS37425SomCableUnclassifiedIPv458
AS328250Golis Telecom SomaliaUnclassifiedIPv458
AS6939Hurricane Electric LLCTransitIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37563SOMTEL INTERNATIONAL LtdUnclassifiedIPv4414
AS328319AMTEL LTDUnclassifiedIPv4116
AS328469Somtel Somalia LTDUnclassifiedIPv4111
AS328954Bluecom LtdUnclassifiedIPv458

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37563SOMTEL INTERNATIONAL LtdUnclassifiedIPv4414
AS30990DJIBOUTI TELECOM S.A.UnclassifiedIPv4 IPv6375
AS37425SomCableUnclassifiedIPv4257
AS328250Golis Telecom SomaliaUnclassifiedIPv4174
AS328469Somtel Somalia LTDUnclassifiedIPv4123
AS328319AMTEL LTDUnclassifiedIPv4116
AS6939Hurricane Electric LLCTransitIPv498
AS37100SEACOM LimitedUnclassifiedIPv4 IPv687
AS328954Bluecom LtdUnclassifiedIPv458

Provenance

Where this comes from

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