IOL-ETHERNET-WAN
Cluster stats
| Netblocks | 16 |
| All fragments | 38 blocks across 18 clusters |
| Cluster ID | 193827645 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
Footprint over time
2 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.80.128.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.129.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.130.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.131.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.132.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.133.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.134.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.135.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.136.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.137.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.138.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.139.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.140.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.141.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.142.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
| 109.80.143.0/24 | IOL-ETHERNET-WAN | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(16 of 16)
RPKI-inferred operator
O2 Czech Republic, a.s.
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
AS5610-MTN
DUMY-RIPE
DUMY-RIPE