Data as of Nov 16, 2026

94.237.108.0/22

15 residential-proxy exits · 30 days

UpCloud Ltd

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
40
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

250 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • 9HTTP
  • ASHBURNPROXIES
  • B2Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • HELODATA
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LudaxProxy
  • MangoProxy
  • NSTPROXY_PRIME
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXIWARE_ECO
  • Proxiware
  • Proxy302
  • Proxyma
  • Q2IP
  • RainProxy
  • RoamProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • 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
94.237.0.0/1732,768FI-UPCLOUD-20081022UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAOct 22, 2008abuse@upcloud.com
└ 94.237.108.0/221,024UPCLOUD-NL-AMS1-NETunknownASSIGNED PAAug 14, 2020abuse@upcloud.com
via FI-UPCLOUD-20081022

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
May 2020
Current origin since
May 2020 · 6.5 yr
Origin networks
1