FanapTelecom-USERS
Cluster stats
| Netblocks | 4 |
| All fragments | 161 blocks across 5 clusters |
| Cluster ID | 192672088 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.200.64.0/21 | FanapTelecom-USERS | RIPE | ASSIGNED PA | ● low |
| 5.200.72.0/21 | FanapTelecom-USERS | RIPE | ASSIGNED PA | ● low |
| 31.24.200.0/22 | FANAPTELECOM-USERS | RIPE | ASSIGNED PA | ● low |
| 31.24.204.0/22 | FANAPTELECOM-USERS | 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
(4 of 4)
RPKI-inferred operator
Tose'h Fanavari Ertebabat Pasargad Arian Co. PJS
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
ir-javidan-1-mnt