asn.dev

Observed topology

AS327885 Viettel-Tanzania

Residential ARIN

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS327885: 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
AS328950Green Telecom LimitedUnclassifiedIPv4975
AS37100SEACOM LimitedUnclassifiedIPv4897
AS329677Telxer Enterprise LimitedUnclassifiedIPv4775
AS37349Aptus Solutions LtdResidentialIPv4631
AS30844Liquid Telecommunications LtdUnclassifiedIPv4597
AS37084Simbanet (T) LimitedResidentialIPv4228
AS328436Flashnet Technologies LimitedResidentialIPv4146
AS17639Converge ICT Solutions Inc.UnclassifiedIPv430
AS38001NewMedia Express Pte LtdHostingIPv430
AS6939Hurricane Electric LLCTransitIPv428

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS327888NMB Bank Public Limited CompanyUnclassifiedIPv41

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS328950Green Telecom LimitedUnclassifiedIPv4975
AS37100SEACOM LimitedUnclassifiedIPv4897
AS329677Telxer Enterprise LimitedUnclassifiedIPv4775
AS37349Aptus Solutions LtdResidentialIPv4631
AS30844Liquid Telecommunications LtdUnclassifiedIPv4598
AS37084Simbanet (T) LimitedResidentialIPv4228
AS328436Flashnet Technologies LimitedResidentialIPv4146
AS17639Converge ICT Solutions Inc.UnclassifiedIPv430
AS38001NewMedia Express Pte LtdHostingIPv430
AS6939Hurricane Electric LLCTransitIPv428

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.