asn.dev

Observed topology

AS37545 Burundi Backbone System SM - Burundi Backbone System SM

Unclassified AFRINIC NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS37545: 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
AS33765TANZANIA TELECOMMUNICATIONS CO. LTDResidentialIPv41,639
AS30844Liquid Telecommunications LtdUnclassifiedIPv41,094

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS37336Leo SA - Econet - Leo SAUnclassifiedIPv4465
AS25429CBINET BurundiUnclassifiedIPv4373
AS37586AS37586UnclassifiedIPv4237
AS37429SPIDERNET SPRL BURUNDIUnclassifiedIPv467
AS20940Akamai International B.V.HostingIPv466
AS63293Facebook, Inc.HostingIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS33765TANZANIA TELECOMMUNICATIONS CO. LTDResidentialIPv42,423
AS30844Liquid Telecommunications LtdUnclassifiedIPv41,567
AS37336Leo SA - Econet - Leo SAUnclassifiedIPv4530
AS25429CBINET BurundiUnclassifiedIPv4373
AS37586AS37586UnclassifiedIPv4237
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv476
AS37429SPIDERNET SPRL BURUNDIUnclassifiedIPv467
AS20940Akamai International B.V.HostingIPv466
AS63293Facebook, Inc.HostingIPv460

Provenance

Where this comes from

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