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

94.237.40.0/21

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

Exits seen per day

698 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.237.41.0/2408
94.237.40.0/2405
94.237.43.0/2405
94.237.45.0/2404
94.237.47.0/2404
94.237.44.0/2403
94.237.42.0/2401
94.237.46.0/2401

Proxy providers listing exits

  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • TrueProxies
  • 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
94.237.0.0/1732,768FI-UPCLOUD-20081022UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAOct 22, 2008abuse@upcloud.com
└ 94.237.40.0/212,048UPCLOUD-NL-AMS1-NET1unknownASSIGNED PAApr 12, 2018abuse@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
Feb 2017
Current origin since
Feb 2017 · 9.7 yr
Origin networks
1