FR-SAAMP-G

BGP inherited
Cluster stats
Netblocks10
All fragments 20 blocks across 2 clusters
Cluster ID211069820
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
83.206.203.92/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
83.206.203.96/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.82.84.60/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.83.41.124/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.83.41.136/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.85.174.220/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.102.4.4/30 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.122.178.24/29 FR-SAAMP-G RIPE ASSIGNED PA ● low
90.122.180.200/29 FR-SAAMP-G RIPE ASSIGNED PA ● low
92.173.170.4/30 FR-SAAMP-G RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FR SAAMP G” — 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.

Network trust

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

NIC Handles

DUMY-RIPE DUMY-RIPE RAIN-TRANSPAC