asn.dev

Observed topology

AS10798 SBICSA

Unclassified AFRINIC

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

Transit

Upstream networks

All 31

Networks observed carrying traffic for AS10798: 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
AS13335Cloudflare, Inc.HostingIPv43,510
AS30844Liquid Telecommunications LtdUnclassifiedIPv4138
AS29614Ghana Telecommunications Company LimitedUnclassifiedIPv4130
AS20294MTN UgandaUnclassifiedIPv4125
AS33763Paratus Telecommunications LimitedUnclassifiedIPv4124
AS37084Simbanet (T) LimitedResidentialIPv4119
AS14988Botswana Telecommunications CorporationUnclassifiedIPv4104
AS37035MIC TANZANIA LTDUnclassifiedIPv467
AS37061Safaricom LimitedUnclassifiedIPv467
AS19711SWAZILAND PTCUnclassifiedIPv465

All 31 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS13335Cloudflare, Inc.HostingIPv43,510
AS30844Liquid Telecommunications LtdUnclassifiedIPv4138
AS29614Ghana Telecommunications Company LimitedUnclassifiedIPv4130
AS20294MTN UgandaUnclassifiedIPv4125
AS33763Paratus Telecommunications LimitedUnclassifiedIPv4124
AS37084Simbanet (T) LimitedResidentialIPv4119
AS14988Botswana Telecommunications CorporationUnclassifiedIPv4104
AS37035MIC TANZANIA LTDUnclassifiedIPv467
AS37061Safaricom LimitedUnclassifiedIPv467
AS19711SWAZILAND PTCUnclassifiedIPv465

All 31 adjacent →

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.