Data as of Nov 11, 2026

46.166.160.0/23

1 residential-proxy exit · 30 days

UAB 'Cherry Servers'

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

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
20
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

135 observations

Proxy providers listing exits

  • B2Proxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • Evomi
  • FloppyData
  • Geonode
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • Shifter
  • 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.160.0/24256BALTICSERVERS-LT-DEDICATEDDedicated serversASSIGNED PAMar 27, 2014abuse@cherryservers.com
via LT-CHERRYSERVERS-20101216
└ 46.166.161.0/24256BALTICSERVERS-LT-DEDICATEDDedicated serversASSIGNED PAMar 27, 2014abuse@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.160.0/21

46.166.160.0/21

Routing history

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

History

Handoffs
1