asn.dev

Observed topology

AS328436 Flashnet-Technologies-Limited

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328436: 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
AS37035MIC TANZANIA LTDUnclassifiedIPv4388
AS37100SEACOM LimitedUnclassifiedIPv4241
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv6204

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32860Cats-Net LimitedUnclassifiedIPv42,045
AS327885Viettel Tanzania PLCResidentialIPv4129
AS329448AZAM MEDIA LIMITEDUnclassifiedIPv441
AS10798The Standard Bank of South Africa (Proprietary) LimitedUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS32860Cats-Net LimitedUnclassifiedIPv42,109
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv61,536
AS37035MIC TANZANIA LTDUnclassifiedIPv4790
AS37100SEACOM LimitedUnclassifiedIPv4538
AS37133Airtel TanzaniaUnclassifiedIPv4261
AS327885Viettel Tanzania PLCResidentialIPv4129
AS329448AZAM MEDIA LIMITEDUnclassifiedIPv441
AS10798The Standard Bank of South Africa (Proprietary) LimitedUnclassifiedIPv413

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.