asn.dev

Observed topology

AS327849 ROCKETNET

Residential AFRINIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS327849: 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
AS37236Reflex SolutionsUnclassifiedIPv4 IPv6275
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6253
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6141
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv615
AS36994VodacomMobileIPv612
AS3741Dimension DataUnclassifiedIPv410
AS58453China Mobile International LimitedUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329276LNX Solutions (Pty) LtdResidentialIPv4 IPv6192
AS329289Novasys IT (Pty) LtdResidentialIPv4121

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS37100SEACOM LimitedUnclassifiedIPv4 IPv6431
AS37236Reflex SolutionsUnclassifiedIPv4 IPv6275
AS37271Workonline Communications(Pty) LtdUnclassifiedIPv4 IPv6264
AS329276LNX Solutions (Pty) LtdResidentialIPv4 IPv6192
AS329289Novasys IT (Pty) LtdResidentialIPv4121
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv621
AS3741Dimension DataUnclassifiedIPv414
AS36994VodacomMobileIPv612
AS58453China Mobile International LimitedUnclassifiedIPv410

Provenance

Where this comes from

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