Data as of Nov 14, 2026

209.50.60.0/22

7 residential-proxy exits · 30 days

UpCloud USA Inc

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

Residential-proxy exits

Proxy exits
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
16
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

52 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
209.50.62.0/2404
209.50.60.0/2402
209.50.63.0/2401

Proxy providers listing exits

  • Byteful
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • Proxyma
  • Shifter
  • VitalExclusive

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
209.50.48.0/204,096UU-7UpCloud USA Inc (UU-7) · USDirect AllocationJan 15, 2016abuse@upcloud.com
└ 209.50.60.0/221,024UPCLOUD-US-SJO1-NETWORK1UpCloud USA San Jose (C07338435) · USReassignedApr 30, 2019abuse@upcloud.com
via UU-7

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
Stable
First seen
Jun 2018
Current origin since
Jun 2018 · 8.4 yr
Origin networks
1