asn.dev

Observed topology

AS329276 LNX-Solutions-Pty-Ltd

Residential LACNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329276: 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
AS327849DIRECTEL COMMUNICATIONS (PTY) LTDResidentialIPv4 IPv6189
AS37468Angola CablesUnclassifiedIPv4 IPv687
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv679
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv610
AS3741Dimension DataUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329181Bluedog TechnologyUnclassifiedIPv4 IPv6309
AS328839Silver Solutions 1234UnclassifiedIPv4121
AS329196iSquared Technologies (Pty) LtdUnclassifiedIPv454

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4 IPv6439
AS329181Bluedog TechnologyUnclassifiedIPv4 IPv6309
AS327849DIRECTEL COMMUNICATIONS (PTY) LTDResidentialIPv4 IPv6189
AS37468Angola CablesUnclassifiedIPv4 IPv6177
AS328839Silver Solutions 1234UnclassifiedIPv4121
AS329196iSquared Technologies (Pty) LtdUnclassifiedIPv454
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv629
AS3741Dimension DataUnclassifiedIPv418

Provenance

Where this comes from

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