FR-9TEL-BACKBONE
Cluster stats
| Netblocks | 18 |
| All fragments | 53 blocks across 10 clusters |
| Cluster ID | 191905601 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 212.30.96.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.97.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.98.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.99.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.100.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.101.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.102.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.103.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.104.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.105.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.106.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.107.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.108.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.109.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.110.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.111.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.112.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
| 212.30.113.0/24 | FR-9TEL-BACKBONE | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
RPKI-inferred operator
Societe Francaise Du Radiotelephone - SFR SA
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
LDCOM-MNT