Data as of Nov 15, 2026

209.50.56.0/22

12 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
12
1.2% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

118 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BirdProxies
  • Byteful
  • CliProxy
  • ColaProxy
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • Infatica
  • LemonPrime
  • LudaxProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • PYPROXY
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • ResiProxies
  • Shifter
  • Thordata
  • VantageProxies
  • ZENPROXY_LITE

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.56.0/221,024UPCLOUD-US-CHI1-NETWORK2UpCloud Chicago Inc (C07056292) · USReassignedSep 4, 2018abuse@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
Mar 2018
Current origin since
Mar 2018 · 8.6 yr
Origin networks
1