Data as of Nov 16, 2026

185.75.237.0/24

12 residential-proxy exits · 30 days

JSC Balticom

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
12
4.7% of its addresses · 30 days
Always-on exits
4
33% of its exits
Providers
48
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

11K observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NovaProxy
  • Oxylabs
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.75.236.0/221,024LV-BALTICOM-20141104JSC Balticom (ORG-JB1-RIPE) · LVALLOCATED PANov 4, 2014abuse@balticom.info
└ 185.75.236.0/23512LV-BALTICOM-185-75unknownASSIGNED PAJan 21, 2020abuse@balticom.info
via LV-BALTICOM-20141104

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 185.75.236.0/22

185.75.236.0/22

Routing history

Pattern
Stable
First seen
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1