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

84.32.188.0/22

45 residential-proxy exits · 30 days

UAB 'Cherry Servers' · space held by UAB Nacionalinis Telekomunikaciju Tinklas

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

Residential-proxy exits

Proxy exits
45
4.4% of its addresses · 30 days
Always-on exits
8
18% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
83
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

17K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.32.188.0/24316
84.32.189.0/2436
84.32.190.0/24214
84.32.191.0/2408

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • Maskify
  • NSocks
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy

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
84.32.0.0/1665,536LT-NTT-20040818UAB Nacionalinis Telekomunikaciju Tinklas (ORG-NTT1-RIPE) · LTALLOCATED PAAug 18, 2004abuse@ntt.lt
└ 84.32.188.0/221,024NTT-CHERRYSERVERSunknownSUB-ALLOCATED PAApr 28, 2021abuse@cherryservers.com
└ 84.32.188.0/24256CloudVPSunknownASSIGNED PAJan 6, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.0/2664CherryServers_dedicatedunknownASSIGNED PAJan 12, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.128/298net-165193-231283-180372unknownASSIGNED PAApr 20, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.136/298net-193595-267999-219363unknownASSIGNED PAApr 5, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.144/298net-197731-273204-275454unknownASSIGNED PAOct 21, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.152/298net-215665-294107-266571unknownASSIGNED PASep 29, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.176/2816net-185938-257936-206328unknownASSIGNED PAJan 3, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.192/298net-218435-297479-277531unknownASSIGNED PAOct 26, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.200/298net-217413-296262-280428unknownASSIGNED PANov 1, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.208/298net-522-111528-124676unknownASSIGNED PAMar 10, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.216/298net-199819-275793-232629unknownASSIGNED PAJun 22, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.224/298net-215102-293442-263480unknownASSIGNED PASep 24, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.232/298net-200948-277307-277675unknownASSIGNED PAOct 26, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.189.240/298net-11895-35685-171681unknownASSIGNED PAJan 2, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.190.0/24256CloudVPSunknownASSIGNED PAFeb 28, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.0/298net-219216-298389-278001unknownASSIGNED PAOct 27, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.8/298net-41759-94609-138427unknownASSIGNED PANov 18, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.16/298net-190551-263992-271707unknownASSIGNED PAOct 13, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.24/298net-522-134320-218842unknownASSIGNED PAApr 3, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.32/298net-184545-255744-201478unknownASSIGNED PANov 24, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.40/298net-165313-231471-180692unknownASSIGNED PAApr 24, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.48/2816net-187653-260303-283278unknownASSIGNED PANov 6, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.64/298net-111833-169931-141957unknownASSIGNED PADec 28, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.72/298net-185104-256691-202863unknownASSIGNED PADec 3, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.80/298net-194210-268823-244869unknownASSIGNED PAAug 9, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.88/298net-219268-298444-278134unknownASSIGNED PAOct 27, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.96/298net-193595-267999-222273unknownASSIGNED PAApr 25, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.104/298net-161155-224537-197907unknownASSIGNED PAOct 16, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.112/298net-156580-217439-166456unknownASSIGNED PAOct 29, 2024abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.120/298net-219608-298833-279217unknownASSIGNED PAOct 29, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.191.128/25128CloudVPSunknownASSIGNED PADec 1, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2021
Current origin since
May 2021 · 5.5 yr
Origin networks
1