LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

94.237.16.0/21

5 residential-proxy exits · 30 days

UpCloud Ltd

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

Residential-proxy exits

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

Exits seen per day

106 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.237.17.0/2402
94.237.16.0/2401
94.237.18.0/2401
94.237.19.0/2401

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • GSocks
  • Geonix
  • Infatica
  • MangoProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter

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.16.0/212,048UPCLOUD-FI-HEL2-NET2UpCloud Cloud ServersASSIGNED PAAug 19, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Aug 2019
Current origin since
Aug 2019 · 7.3 yr
Origin networks
1