Observed topology

AS37196 Expresso Senegal SA - Expresso Senegal SA

Unclassified APNIC

Upstreams 4 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 0

Upstream graph Who carries AS37196, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS37196 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37196: 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.

AS	Network	Type	Families	Paths seen
AS204523	Expresso Telecom Group Ltd	Unclassified	IPv4	596
AS37613	DOLPHIN TELECOMMUNICATION LIMITED	Unclassified	IPv4	589
AS8657	SERVICOS DE COMUNICACOES E MULTIMEDIA S.A.	Unclassified	IPv4	334
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	105

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS328650	Universite numerique Cheikh Hamidou KANE (UN-CHK)	Unclassified	IPv4	57

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS204523	Expresso Telecom Group Ltd	Unclassified	IPv4	596
AS37613	DOLPHIN TELECOMMUNICATION LIMITED	Unclassified	IPv4	589
AS8657	SERVICOS DE COMUNICACOES E MULTIMEDIA S.A.	Unclassified	IPv4	391
AS60171	AFR-IX TELECOM S.A.	Unclassified	IPv4	105
AS328650	Universite numerique Cheikh Hamidou KANE (UN-CHK)	Unclassified	IPv4	57

Provenance

Where this comes from

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