FR-AIGLE

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

Footprint over time

3 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-12

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
81.80.206.208/29 FR-AIGLE-INTERNATIONAL RIPE ASSIGNED PA ● low
81.252.196.64/28 FR-AIGLE RIPE ASSIGNED PA ● low
81.252.215.120/29 FR-AIGLE RIPE ASSIGNED PA ● low
90.102.69.152/29 FR-AIGLE-INTERNATIONAL RIPE ASSIGNED PA ● low
194.206.71.32/29 FR-SA-AIGLE-INTERNATIONAL RIPE ASSIGNED PA ● low
194.206.228.224/29 FR-AIGLE RIPE ASSIGNED PA ● low
217.108.123.32/30 FR-AIGLE-INTERNATIONAL RIPE ASSIGNED PA ● low
217.108.123.244/30 FR-SA-AIGLE-INTERNATIONAL RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FR AIGLE” — 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 (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

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