asn.dev

Observed topology

AS328112 Linux-Based-Systems-Design-AS

Unclassified AFRINIC

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS328112: 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 IPv6494
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6188
AS6939Hurricane Electric LLCTransitIPv6176
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6171
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS3741Dimension DataUnclassifiedIPv412
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv65
AS9002RETN LimitedUnclassifiedIPv64
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS328474Jebo Connect Pty LtdUnclassifiedIPv4 IPv61,114

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS328474Jebo Connect Pty LtdUnclassifiedIPv4 IPv61,114
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv61,071
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6461
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6391
AS6939Hurricane Electric LLCTransitIPv4 IPv6220
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS3741Dimension DataUnclassifiedIPv412
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv65
AS9002RETN LimitedUnclassifiedIPv64

Provenance

Where this comes from

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