Data as of Nov 14, 2026

94.237.112.0/21

11 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
11
0.54% of its addresses · 30 days
Spread
4 of 8
/24s with at least one exit
Providers
30
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

201 observations

/24s with the most always-on exits

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonode
  • HELODATA
  • HideProxy
  • IPFly
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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
94.237.0.0/1732,768FI-UPCLOUD-20081022UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAOct 22, 2008abuse@upcloud.com
└ 94.237.112.0/212,048UPCLOUD-FI-HEL1-NET5UpCloud Cloud ServersASSIGNED PAFeb 11, 2019abuse@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
Feb 2019
Current origin since
Feb 2019 · 7.8 yr
Origin networks
1