asn.dev

Observed topology

AS327799 VIETTEL BURUNDI SA - VIETTEL BURUNDI SA

Unclassified AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS327799: 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
AS36890MTN RwandacellUnclassifiedIPv42,164
AS37273Bandwidth and Cloud Services Group LtdResidentialIPv4628
AS33765TANZANIA TELECOMMUNICATIONS CO. LTDResidentialIPv4544
AS30844Liquid Telecommunications LtdUnclassifiedIPv4319
AS2University of DelawareUnclassifiedIPv440

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25429CBINET BurundiUnclassifiedIPv4134

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS36890MTN RwandacellUnclassifiedIPv42,228
AS37273Bandwidth and Cloud Services Group LtdResidentialIPv4658
AS33765TANZANIA TELECOMMUNICATIONS CO. LTDResidentialIPv4544
AS30844Liquid Telecommunications LtdUnclassifiedIPv4359
AS25429CBINET BurundiUnclassifiedIPv4134
AS2University of DelawareUnclassifiedIPv440

Provenance

Where this comes from

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