iYoRoy-Network
Data as of 2026-09-20
Handle
This organisation
| Netblocks | 13 |
| IPv6 | 13 prefixes (largest 2001:504:125:e1::aafa/128) |
| Also registered under this name | 18 netblocks across 6 separate records |
| Record ID | 242516298 |
| 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 (13)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2001:504:125:e1::aafa/128 | iYoRoy-Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:aa::188/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 (13)
Footprint over time
13 weekly snapshots · JSON
13
+2 netblocks since 2026-07-05
2026-07-05
peak 13
2026-09-20
Network trust
what's this?
RPKI hygiene: D
how networks compare →
46.2%
of checked blocks have valid RPKI ROA coverage
(6 of 13)
No discrepancies found among checked blocks.
NIC Handles
AS205369