asn.dev

Observed topology

AS328512 Backspace-Technologies

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS328512: 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
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv6199
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6179
AS5713Telkom SA Ltd.UnclassifiedIPv4 IPv673
AS6939Hurricane Electric LLCTransitIPv4 IPv670
AS3741Dimension DataUnclassifiedIPv49
AS37721Virtual Technologies & SolutionsResidentialIPv46
AS23764CTGNetUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329248Simtel ISPUnclassifiedIPv4 IPv6166

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv6281
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6230
AS329248Simtel ISPUnclassifiedIPv4 IPv6166
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS5713Telkom SA Ltd.UnclassifiedIPv4 IPv673
AS3741Dimension DataUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv48
AS23764CTGNetUnclassifiedIPv44
AS32437Webdev CC T/A CybertekResidentialIPv41

Provenance

Where this comes from

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