MIDASPLAYER COM LTD
MIDASPLAYER-COM-LTD
Registry
Cluster stats
| Netblocks | 4 |
| All fragments | 23 blocks across 5 clusters |
| Cluster ID | 194130082 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 193.240.16.32/29 | MIDASPLAYER-COM-LTD | RIPE | ASSIGNED PA | ● low |
| 194.74.138.80/29 | MIDASPLAYER-COM-LTD | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:17ed::/48 | MIDASPLAYER-COM-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:17ed::/56 | MIDASPLAYER-COM-LTD | RIPE | ASSIGNED | ● 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 (2)
These blocks are registered to MIDASPLAYER COM LTD 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:17ed::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:17ed::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
LEVEL3-MNT
QUZAUK