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

5.199.171.0/24

9 residential-proxy exits · 30 days

UAB 'Cherry Servers'

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
37
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonode
  • IPFly
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalExclusive

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.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