Mi-JaNET
Data as of 2026-09-06
Handle
This organisation
| Netblocks | 4 |
| IPv6 | 2 prefixes (largest 2001:7f8:14::ab:1/128) |
| Record ID | 239848816 |
| Registry | PEERINGDB |
| Customers | see who runs inside 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.210.16.98/32 | Mi-JaNET | PEERINGDB | ASSIGNED | ● high |
| 185.0.20.35/32 | Mi-JaNET | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:14::ab:1/128 | Mi-JaNET | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:7f::35/128 | Mi-JaNET | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS204917