iYoRoy-Network
Data as of 2026-08-23
Handle
Cluster stats
| Netblocks | 12 |
| IPv6 | 12 prefixes (largest 2001:504:125:e1::aafa/128) |
| All fragments | 17 blocks across 6 clusters |
| Cluster ID | 229201005 |
| 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
9 weekly snapshots · JSON
12
+1 netblocks since 2026-07-05
2026-07-05
peak 12
2026-08-23
IP Ranges (12)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:504:125:e1::aafa/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1:0:20:5369:1/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0::3:2239:1/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2401:2060:b109:156::10a/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:20:5369:1/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f429:31::1a/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315::1d/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f92a:1315:2::34/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:16::140/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2a0e:8f01:1000:24::194/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:7803:fc60:aaaa::2053:69/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2a14:67c1:a080::3224/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (12)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(6 of 12)
No discrepancies found among checked blocks.
NIC Handles
AS205369