Data as of Nov 16, 2026

95.161.216.0/23

6 residential-proxy exits · 30 days

'Eneva' Ltd

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
1.2% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
38
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.161.217.0/2404
95.161.216.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyStyler
  • Proxying
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.161.216.0/23512RU-ENEVA-20081223"Eneva" Ltd (ORG-LA2077-RIPE) · RUALLOCATED PAFeb 27, 2026abuse@eneva.ru
└ 95.161.216.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@eneva.ru
via RU-ENEVA-20081223
└ 95.161.217.0/24256OBIT-LANObit, Ltd.LIR-PARTITIONED PAJun 25, 2024abuse@eneva.ru
via RU-ENEVA-20081223

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jan 2018
Current origin since
Mar 2026 · 8 mo
Origin networks
2
Last change of origin
Mar 2026
Recorded history

History

Handoffs
1