asn.dev

Observed topology

AS37098 globe-as

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37098: 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
AS37294TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv4607
AS37440Airtel Malawi LtdUnclassifiedIPv4403
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv6171
AS327708Airtel Rwanda LtdUnclassifiedIPv4137

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328403Malawi Revenue AuthorityUnclassifiedIPv465
AS328565NBS BANK PLCUnclassifiedIPv464
AS328738Youth Net and CounsellingUnclassifiedIPv4 IPv664
AS329335Department of HIV & AIDS and Viral HepatitisUnclassifiedIPv443

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37294TELEKOM NETWORKS MALAWI LTDUnclassifiedIPv4703
AS37440Airtel Malawi LtdUnclassifiedIPv4480
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4 IPv6208
AS327708Airtel Rwanda LtdUnclassifiedIPv4137
AS328403Malawi Revenue AuthorityUnclassifiedIPv465
AS328565NBS BANK PLCUnclassifiedIPv464
AS328738Youth Net and CounsellingUnclassifiedIPv4 IPv664
AS329335Department of HIV & AIDS and Viral HepatitisUnclassifiedIPv443
AS37187Inq. Digital LimitedUnclassifiedIPv426

Provenance

Where this comes from

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