Data as of Nov 18, 2026

185.8.104.0/23

2 residential-proxy exits · 30 days

UAB 'Cherry Servers'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
27
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

431 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • VitalProxy

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
185.8.104.0/221,024LT-CHERRYSERVERS-20121030UAB "Cherry Servers" (ORG-UDC69-RIPE) · LTALLOCATED PAOct 30, 2012abuse@cherryservers.com
└ 185.8.104.128/25128BALTICSERVERS-LT-DEDICATEDunknownASSIGNED PAJun 27, 2019abuse@cherryservers.com
via LT-CHERRYSERVERS-20121030
└ 185.8.105.0/2664cherryservers-redirunknownASSIGNED PASep 30, 2021abuse@cherryservers.com
via LT-CHERRYSERVERS-20121030
└ 185.8.105.64/2664VPS-IPsunknownASSIGNED PAFeb 28, 2022abuse@cherryservers.com
via LT-CHERRYSERVERS-20121030
└ 185.8.105.128/25128VPS-IPsunknownASSIGNED PAJan 17, 2022abuse@cherryservers.com
via LT-CHERRYSERVERS-20121030

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
Stable
First seen
Aug 2013
Current origin since
Jan 2015 · 12 yr
Origin networks
2
Last change of origin
Jan 2015
Recorded history

History

Handoffs
2