Data as of Nov 14, 2026

84.32.128.0/22

23 residential-proxy exits · 30 days

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

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
23
2.2% of its addresses · 30 days
Always-on exits
1
4.3% of its exits
Spread
2 of 4
/24s with at least one exit
Providers
59
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.32.129.0/24112
84.32.131.0/24011

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • WealthProxies

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
84.32.130.0/24
since Jul 2024
AS204770HostingUAB Nacionalinis Telekomunikaciju Tinklas
84.32.131.0/24
since Dec 2023
AS204770Hosting11UAB Nacionalinis Telekomunikaciju Tinklas

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.128.0/221,024NTT-CHERRYSERVERSunknownSUB-ALLOCATED PAJun 30, 2022abuse@cherryservers.com
└ 84.32.128.0/24256CloudVPSunknownASSIGNED PASep 13, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.129.0/24256floating-ip-rangeunknownASSIGNED PASep 13, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.0/298net-26689-78010-118619unknownASSIGNED PADec 30, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.8/298net-114866-219780-169047unknownASSIGNED PADec 3, 2024abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.16/2816net-522-85191-113585unknownASSIGNED PAOct 17, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.40/298net-522-123001-125474unknownASSIGNED PAMar 27, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.48/298net-202985-279622-281801unknownASSIGNED PANov 4, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.56/298net-26689-78010-118621unknownASSIGNED PADec 30, 2022abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.64/298net-26689-78010-124303unknownASSIGNED PAMar 3, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.72/298net-156931-217949-229679unknownASSIGNED PAJun 8, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.80/2816net-93443-150715-128730unknownASSIGNED PAMay 1, 2023abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.96/298net-156931-217949-165750unknownASSIGNED PAOct 18, 2024abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.112/298net-195983-271073-231112unknownASSIGNED PAJun 15, 2026abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.120/298net-176912-245258-189835unknownASSIGNED PAJul 30, 2025abuse@cherryservers.com
via NTT-CHERRYSERVERS
└ 84.32.130.240/298net-181818-251805-206218unknownASSIGNED PAJan 2, 2026abuse@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

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
May 2005
Current origin since
Sep 2022 · 4.2 yr
Origin networks
3
Last change of origin
Sep 2022
Recorded history

History

Handoffs
2