Observed topology

AS328576 TelcoExchange

Residential AFRINIC

Upstreams 5 carry this network

Downstreams 2 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 3

Upstream graph Who carries AS328576, and who carries them, drawn as a map up to the transit-free core. 6 exchanges Where AS328576 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328576: 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.

AS	Network	Type	Families	Paths seen
AS22355	Frogfoot Networks	Residential	IPv4 IPv6	668
AS174	Cogent Communications, LLC	Transit	IPv4	645
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	466
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	38
AS3741	Dimension Data	Unclassified	IPv4	23

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS37515	iConnectSA (Pty) Ltd	Residential	IPv4	2,114
AS64519	unnamed	Unclassified	IPv4	2

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS37515	iConnectSA (Pty) Ltd	Residential	IPv4	2,344
AS22355	Frogfoot Networks	Residential	IPv4 IPv6	2,067
AS174	Cogent Communications, LLC	Transit	IPv4	1,531
AS6939	Hurricane Electric LLC	Transit	IPv4 IPv6	476
AS3741	Dimension Data	Unclassified	IPv4	73
AS37721	Virtual Technologies & Solutions	Residential	IPv4 IPv6	39
AS64519	unnamed	Unclassified	IPv4	2

Provenance

Where this comes from

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