FR-SAPAC--LB_INTERNET

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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.252.36.26/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.85.89.35/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.85.216.230/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.115.174.113/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.121.161.7/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.121.163.239/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.121.168.86/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
90.121.168.87/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low
92.173.240.248/32 FR-SAPAC--LB_INTERNET RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FR SAPAC” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE PC80199-MNT RAIN-TRANSPAC