I6P_Project_RU
Data as of 2026-09-20
BGP inherited
This organisation
| Netblocks | 5 |
| IPv6 | 5 prefixes (largest 2a0f:cdc6:2000::/44) |
| Also registered under this name | 6 netblocks across 2 separate records |
| Record ID | 241025433 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0e:b107:279c::/46 | I6P-Project-RU | RIPE | ASSIGNED | ● low |
| 2a0f:cdc6:2000::/44 | I6P_Project_RU | RIPE | ASSIGNED | ● low |
| 2a0f:cdc6:2010::/44 | I6P_Project_RU | RIPE | ASSIGNED | ● low |
| 2a0f:cdc6:5010::/44 | I6P_Project_RU | RIPE | ASSIGNED | ● low |
| 2a0f:cdc6:5020::/44 | I6P_Project_RU | RIPE | ASSIGNED | ● low |
IPv6 ranges (5)
Network trust
what's this?
RPKI hygiene: D
how networks compare →
20.0%
of checked blocks have valid RPKI ROA coverage
(1 of 5)
RPKI-inferred operator
SYMEXO SAS
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
I6P-MNT
ITNETPASS-MNT
TUNNELNETPASS-MNT