asn.dev

Observed topology

AS328471 HERO TELECOMS (PTY) LTD - HERO TELECOMS (PTY) LTD

Mobile AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328471: 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
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv65,057
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv43,595
AS6939Hurricane Electric LLCTransitIPv4 IPv63,144
AS37468Angola CablesUnclassifiedIPv4 IPv6434
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6197
AS3741Dimension DataUnclassifiedIPv4196
AS36994VodacomMobileIPv622

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329300HEROTEL BUSINESS (PTY) LTDUnclassifiedIPv4 IPv6152

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS30844Liquid Telecommunications LtdUnclassifiedIPv4 IPv65,103
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv43,639
AS6939Hurricane Electric LLCTransitIPv4 IPv63,202
AS37468Angola CablesUnclassifiedIPv4 IPv6434
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv6199
AS3741Dimension DataUnclassifiedIPv4198
AS329300HEROTEL BUSINESS (PTY) LTDUnclassifiedIPv4 IPv6152
AS36994VodacomMobileIPv622

Provenance

Where this comes from

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