PERENCO

BGP inherited
Cluster stats
Netblocks9
All fragments 15 blocks across 3 clusters
Cluster ID205587252
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

4 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-13

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.70.136.0/28 PER-SITE13 RIPE ASSIGNED PA ● medium
77.70.143.16 – 77.70.143.95 PERENCO RIPE ASSIGNED PA ● medium
77.70.156.224/30 PERENCO RIPE ASSIGNED PA ● medium
77.70.157.32/29 PERENCO RIPE ASSIGNED PA ● medium
77.70.157.80/30 PERENCO RIPE ASSIGNED PA ● medium
94.31.43.64/26 Net-Perenco RIPE ASSIGNED PA ● low
193.160.88.64/26 Net-Perenco RIPE ASSIGNED PA ● low
193.160.88.128/26 Net-Perenco RIPE ASSIGNED PA ● low
2a00:2381:1183::/48 PERENCO RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to PERENCO but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:2381:1183::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

ABOVENET-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE Marlink-MNT PA11071-RIPE