MIR LTD
MIR-LTD
Registry
Cluster stats
| Netblocks | 8 |
| All fragments | 167 blocks across 48 clusters |
| Cluster ID | 191931481 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 5 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-06
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.121.1.192/29 | MIR-LIMITED | RIPE | ASSIGNED PA | ● low |
| 80.237.33.96/28 | MIR-NET | RIPE | ASSIGNED PA | ● low |
| 81.128.229.248/29 | MIR-LTD | RIPE | ASSIGNED PA | ● low |
| 88.210.19.0/24 | Mir | RIPE | ASSIGNED PA | ● low |
| 217.141.155.200/29 | MIR-SRL | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:effc::/56 | MIR-LTD | RIPE | ASSIGNED | ● low |
| 2a00:2381:effc::/48 | MIR-LTD | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:effc:300::/56 | MIR-LIMITED | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
87.5%
of checked blocks have valid RPKI ROA coverage
(7 of 8)
Possible discrepancies (4)
These blocks are registered to MIR-LTD but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:2381:effc::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:effc::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:effc:300::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
| 88.210.19.0/24 /24 | authorized for AS25308 — CityLanCom LTD |
NIC Handles
BTNET-MNT
CITYLAN-MNT
DUMY-RIPE
DUMY-RIPE
INTERB-MNT
TRANSTELECOM-MNT