FR-TELEMUS-2B
Cluster stats
| Netblocks | 19 |
| All fragments | 289,016 blocks across 133,243 clusters |
| Cluster ID | 194090164 |
| 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 (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:688:fe00::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe01::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe02::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe03::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe04::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe05::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe06::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe07::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe08::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe09::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0a::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0b::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0c::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0d::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0e::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe0f::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe10::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe11::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
| 2001:688:fe12::/48 | FR-TELEMUS-2B | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
RPKI-inferred operator
Orange S.A.
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
FT-BRX