NAPAfrica Route Servers

Data as of 2026-09-20
BGP inherited
This organisation
Netblocks16
IPv6 8 prefixes (largest 2001:43f8:6d0::1/128)
Record ID242146894
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 2 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
196.10.141.2/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
196.10.141.3/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
196.60.9.1/32 NAPAfrica Route Collectors PEERINGDB ASSIGNED ● high
196.60.9.2/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
196.60.9.3/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
196.60.70.1/32 NAPAfrica Route Collectors PEERINGDB ASSIGNED ● high
196.60.70.2/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
196.60.70.3/32 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d0::1/128 NAPAfrica Route Collectors PEERINGDB ASSIGNED ● high
2001:43f8:6d0::2/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d0::3/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d1::1/128 NAPAfrica Route Collectors PEERINGDB ASSIGNED ● high
2001:43f8:6d1::2/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d1::3/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d2::2/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high
2001:43f8:6d2::3/128 NAPAfrica Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (8)

Footprint over time

13 weekly snapshots · JSON
16 0 netblocks since 2026-07-05
2026-07-05 peak 16 2026-09-20

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (16 of 16)
No discrepancies found among checked blocks.

NIC Handles

AS37186 AS37195