asn.dev

Observed topology

AS329029 MyManga-AS

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS329029: 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
AS6774Belgacom International Carrier Services SAUnclassifiedIPv4 IPv6288
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv457
AS6939Hurricane Electric LLCTransitIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS329664AGAPETECH_ENTERPRISE_SOLUTION_LIMITEDUnclassifiedIPv4 IPv6409
AS329658NetPoint-SolutionsUnclassifiedIPv4192
AS329671PERK_GROUP_AFRICA_LIMITEDUnclassifiedIPv4189
AS329737Azanet_Solutions_LimitedUnclassifiedIPv463
AS329749AIRNET-BROADBANDUnclassifiedIPv459

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6774Belgacom International Carrier Services SAUnclassifiedIPv4 IPv6819
AS60171AFR-IX TELECOM S.A.UnclassifiedIPv4438
AS329664AGAPETECH_ENTERPRISE_SOLUTION_LIMITEDUnclassifiedIPv4 IPv6409
AS329658NetPoint-SolutionsUnclassifiedIPv4192
AS329671PERK_GROUP_AFRICA_LIMITEDUnclassifiedIPv4189
AS329737Azanet_Solutions_LimitedUnclassifiedIPv463
AS329749AIRNET-BROADBANDUnclassifiedIPv459
AS6939Hurricane Electric LLCTransitIPv61

Provenance

Where this comes from

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