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

94.237.48.0/20

27 residential-proxy exits · 30 days

UpCloud Ltd

Announcement
this exact prefix
RPKI valid
Announced by
AS202053
Type
Hosting

Residential-proxy exits

Proxy exits
27
0.66% of its addresses · 30 days
Spread
13 of 16
/24s with at least one exit
Providers
38
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

601 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.237.53.0/2404
94.237.54.0/2403
94.237.61.0/2403
94.237.60.0/2402
94.237.49.0/2402
94.237.50.0/2402
94.237.48.0/2402
94.237.62.0/2402
94.237.57.0/2402
94.237.51.0/2401
94.237.59.0/2401
94.237.58.0/2401
94.237.52.0/2401

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • 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
94.237.0.0/1732,768FI-UPCLOUD-20081022UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAOct 22, 2008abuse@upcloud.com
└ 94.237.48.0/212,048UPCLOUD-UK-LON1-NET3UpCloud Cloud ServersASSIGNED PAApr 12, 2018abuse@upcloud.com
via FI-UPCLOUD-20081022
└ 94.237.56.0/212,048UPCLOUD-UK-LON1-NET4UpCloud Cloud ServersASSIGNED PAOct 31, 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
Apr 2019
Current origin since
Apr 2019 · 7.6 yr
Origin networks
1