ESOO-NET
BGP inherited
Cluster stats
| Netblocks | 7 · 8,321 IPv4 addresses |
| Cluster ID | 208933099 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 85.192.128.0 – 85.192.140.31 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 85.192.140.144/29 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 85.192.140.160/27 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 85.192.140.224 – 85.192.149.31 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 213.135.114.0 – 213.135.122.127 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 213.135.122.128 – 213.135.124.255 | ESOO-NET | RIPE | ASSIGNED PA | ● low |
| 213.135.125.0/24 | ESOO-NET | 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
(7 of 7)
Possible discrepancies (5)
These blocks are registered to ESOO-NET but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 85.192.128.0 – 85.192.140.31 /20 | authorized for AS12389 — PJSC Rostelecom |
| 213.135.114.0 – 213.135.122.127 /21 | authorized for AS12389 — PJSC Rostelecom |
| 85.192.140.224 – 85.192.149.31 /21 | authorized for AS12389 — PJSC Rostelecom |
| 213.135.122.128 – 213.135.124.255 /23 | authorized for AS12389 — PJSC Rostelecom |
| 213.135.125.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ESOO-MNT