Data as of Nov 12, 2026

5.22.208.0/22

20 residential-proxy exits · 30 days

UpCloud Ltd

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting

Residential-proxy exits

Proxy exits
20
2.0% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
36
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

210 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.22.211.0/2406
5.22.208.0/2405
5.22.209.0/2403
5.22.210.0/2402

Proxy providers listing exits

  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VantageProxies
  • VitalExclusive
  • 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
5.22.208.0/204,096FI-UPCLOUD-20120504UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAMay 29, 2020abuse@upcloud.com
└ 5.22.208.0/221,024UPCLOUD-NL-AMS1-NETunknownASSIGNED PAApr 22, 2021abuse@upcloud.com
via FI-UPCLOUD-20120504

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
Jan 2025
Current origin since
Jan 2025 · 1.8 yr
Origin networks
1