JMDI
Data as of 2026-07-26
Handle
Cluster stats
| Netblocks | 6 |
| IPv6 | 1 prefix (largest 2001:678:3ac::511/128) |
| All fragments | 71 blocks across 3 clusters |
| Cluster ID | 214590443 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
6
-2 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-26
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.46.145.138/32 | JMDI | PEERINGDB | ASSIGNED | ● high |
| 185.1.199.18/32 | JMDI | PEERINGDB | ASSIGNED | ● high |
| 195.149.233.191/32 | JMDI | PEERINGDB | ASSIGNED | ● high |
| 195.182.218.214/32 | JMDI | PEERINGDB | ASSIGNED | ● high |
| 212.91.0.151/32 | JMDI | PEERINGDB | ASSIGNED | ● high |
| 2001:678:3ac::511/128 | JMDI | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (1)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(3 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS41676