asn.dev

Observed topology

AS36955 Matrix-ASN1

Unclassified AFRINIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36955: 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
AS15964CAMTELHostingIPv41,185
AS3491PCCW Global (HK) Ltd.TransitIPv4705
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4261
AS36905Creolink CommunicationsUnclassifiedIPv466

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328866NEWTELNET CAMEROUN SASUnclassifiedIPv41,898
AS329470Afriland First BankUnclassifiedIPv4190
AS328920AFRICA DATA CENTER SAUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3491PCCW Global (HK) Ltd.TransitIPv41,958
AS328866NEWTELNET CAMEROUN SASUnclassifiedIPv41,898
AS15964CAMTELHostingIPv41,782
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4500
AS329470Afriland First BankUnclassifiedIPv4190
AS36905Creolink CommunicationsUnclassifiedIPv4125
AS328920AFRICA DATA CENTER SAUnclassifiedIPv460

Provenance

Where this comes from

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