PURPLE
Cluster stats
| Netblocks | 4 |
| All fragments | 144 blocks across 37 clusters |
| Cluster ID | 191903643 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.218.30.60/30 | PURPLE | RIPE | ASSIGNED PA | ● low |
| 93.104.231.120/29 | PURPLE-NET | RIPE | ASSIGNED PA | ● low |
| 195.193.34.0/29 | PURPLE | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:6fd::/48 | PURPLE-COMMUNICATIONS | RIPE | AGGREGATED-BY-LIR | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
Possible discrepancies (1)
These blocks are registered to PURPLE 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.
| 2a00:2381:6fd::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
KNIC-MNT
MNET-MNT
NLNET-MNT