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

5.199.170.0/23

20 residential-proxy exits · 30 days

UAB 'Cherry Servers'

Announcement
5.199.168.0/22
RPKI valid
Announced by
AS16125
Type
Hosting

Residential-proxy exits

Proxy exits
20
3.9% of its addresses · 30 days
Always-on exits
3
15% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
54
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

7.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.199.170.0/2427
5.199.171.0/24112

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
5.199.170.0/24
since Sep 28, 2026
AS16125Hosting7
2 always on
UAB "Cherry Servers"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
5.199.160.0/204,096LT-CHERRYSERVERS-20120828UAB "Cherry Servers" (ORG-UDC69-RIPE) · LTALLOCATED PAAug 28, 2012abuse@cherryservers.com
└ 5.199.170.0/24256Dedicated_ServersunknownASSIGNED PAMar 9, 2022abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.0/25128Floating-IPsunknownASSIGNED PAAug 3, 2018abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.128/2816net-79139-135405-224375unknownASSIGNED PAMay 11, 2026abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.144/298net-18553-55659-98934unknownASSIGNED PAMar 6, 2022abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.160/2732net-18553-55659-91687unknownASSIGNED PAJul 1, 2021abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.192/298net-190394-263787-259930unknownASSIGNED PASep 18, 2026abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.200/298net-28575-297564-275371unknownASSIGNED PAOct 21, 2026abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.208/298floragroupFloraCloud (ORG-FA917-RIPE)ASSIGNED PAApr 1, 2019abuse@floragroup.net
└ 5.199.171.216/298net-215442-293833-265512unknownASSIGNED PASep 27, 2026abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.224/298FloraCloudFloraCloud (ORG-FA917-RIPE)ASSIGNED PAOct 24, 2018abuse@floragroup.net
└ 5.199.171.240/298net-108284-217348-165107unknownASSIGNED PAOct 9, 2024abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828
└ 5.199.171.248/298net-108284-217348-165115unknownASSIGNED PAOct 9, 2024abuse@cherryservers.com
via LT-CHERRYSERVERS-20120828

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

5.199.168.0/22

Routing history

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

History

Handoffs
2