Data as of Nov 19, 2026

85.9.214.0/24

4 residential-proxy exits · 30 days

UpCloud Ltd

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
34
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

131 observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BirdProxies
  • BottingTools
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • HPROXY
  • HideProxy
  • Infatica
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Seller
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • Q2IP
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
85.9.192.0/198,192FI-UPCLOUD-20050216UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAFeb 20, 2025abuse@upcloud.com
└ 85.9.208.0/212,048UPCLOUD-NL-AMS1-NETUpCloud Cloud ServersSUB-ALLOCATED PAMar 14, 2025abuse@upcloud.com
via FI-UPCLOUD-20050216
└ 85.9.212.0/221,024UPCLOUD-NL-AMS1-NETUpCloud Cloud ServersASSIGNED PAMar 20, 2026abuse@upcloud.com
via UPCLOUD-NL-AMS1-NET

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 85.9.208.0/21

85.9.208.0/21

Routing history

Pattern
Reactivated
First seen
Jun 2013
Current origin since
Mar 2025 · 1.7 yr
Origin networks
5
Last change of origin
Mar 2025
Recorded history

History

Handoffs
4