Data as of Nov 11, 2026

46.166.169.0/24

10 residential-proxy exits · 30 days

UAB 'Cherry Servers'

Announcement
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium
Proxy exits nearby

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
4
40% of its exits
Providers
43
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

8.8K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
46.166.160.0/204,096LT-CHERRYSERVERS-20101216UAB "Cherry Servers" (ORG-UDC69-RIPE) · LTALLOCATED PAOct 2, 2013abuse@cherryservers.com
└ 46.166.169.0/24256BALTICSERVERS-LT-DEDICATEDDedicated serversASSIGNED PAMar 20, 2015abuse@cherryservers.com
via LT-CHERRYSERVERS-20101216

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 46.166.168.0/21

46.166.168.0/21

Routing history

Pattern
Stable
First seen
Apr 2014
Current origin since
Jan 2015 · 12 yr
Origin networks
2
Last change of origin
Jan 2015
Recorded history

History

Handoffs
2