vultr_jp
Data as of 2026-08-09
Handle
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a12:3fc2:ab70::/48) |
| Cluster ID | 220534010 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a12:3fc2:ab70::/48 | vultr_jp | RIPE | ASSIGNED | ● low |
| 2a13:a5c7:2103::/48 | Vultr-JP | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
RPKI-inferred operator
Puhe You
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
PA733NETWORKS-MNT
radishcloud-MNT