V6Direct
Registry
Cluster stats
| Netblocks | 4 |
| All fragments | 5 blocks across 2 clusters |
| Cluster ID | 193390907 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.175.223.30/32 | V6Direct | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:134::76/128 | V6Direct | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:1::28/128 | V6Direct | PEERINGDB | ASSIGNED | ● high |
| 2a14:7580:ec00::5/128 | V6Direct | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
75.0%
of checked blocks have valid RPKI ROA coverage
(3 of 4)
No discrepancies found among checked blocks.
NIC Handles
AS199746