OKS-LAN
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 204644231 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| 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 |
|---|---|---|---|---|
| 46.47.232.200/30 | OKS-LAN | RIPE | ASSIGNED PA | ● low |
| 81.3.164.224/29 | OKS-LAN | RIPE | ASSIGNED PA | ● low |
| 93.153.236.176/29 | OKS-LAN | RIPE | ASSIGNED PA | ● low |
| 109.124.90.112/28 | OKS-LAN | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- PROKS-LAN via "OBIT" Ltd. sub-allocation
- Echotoks-LAN via PJSC MegaFon sub-allocation
- DOKS-LAN via "OBIT" Ltd. sub-allocation
- Radoks-LAN via PJSC MegaFon sub-allocation
- VOKS-LAN via PJSC MegaFon sub-allocation
- RADIO-ROKS-LAN via PJSC MegaFon sub-allocation
- Voks via PJSC MegaFon sub-allocation
- Smartboks via PJSC MegaFon sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
PSTAR-MNT