LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

94.236.233.0/24

39 residential-proxy exits · 30 days

Dilis Grup EOOD · space held by OPTICCOM- BULGARIA Ltd.

Announcement
this exact prefix
No RPKI
Announced by
AS197304
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
39
15% of its addresses · 30 days
Always-on exits
7
18% of its exits
Providers
72
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

7.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PrivateByte
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
94.236.232.0/23512BG-OPTIC-COM-20081021OPTICCOM- BULGARIA Ltd. (ORG-DE13-RIPE) · BGALLOCATED PAOct 24, 2016abuse@optic-com.eu
└ 94.236.233.0/24256BG-OPTIC-COM-NETDilisNetASSIGNED PAApr 29, 2011abuse@optic-com.eu
via BG-OPTIC-COM-20081021

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2011
Current origin since
Feb 2019 · 7.8 yr
Origin networks
2
Last change of origin
Feb 2019
Recorded history

History

Handoffs
1