UP-FTS-NET
Handle
Cluster stats
| Netblocks | 5 |
| All fragments | 410 blocks across 120 clusters |
| Cluster ID | 192532570 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 95.87.135.64/26 | UP-FTS-NET | RIPE | ASSIGNED PA | ● low |
| 95.87.137.0/24 | UP-FTS-NET | RIPE | ASSIGNED PA | ● low |
| 193.2.61.224/28 | UP-FTS-NET | RIPE | ASSIGNED PA | ● low |
| 212.235.220.208/28 | UP-FTS-NET | RIPE | ASSIGNED PA | ● low |
| 212.235.243.112/28 | UP-FTS-NET | 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
(5 of 5)
Possible discrepancies (1)
These blocks are registered to UP-FTS-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 95.87.137.0/24 /24 | authorized for AS2107 — ARNES |
NIC Handles
ARNES-MNT
DUMY-RIPE
DUMY-RIPE