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

80.69.172.0/22

7 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
7
0.68% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

244 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
80.69.173.0/2403
80.69.172.0/2402
80.69.175.0/2402

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • NodeProxy
  • NovaProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
80.69.172.0/221,024FI-UPCLOUD-20090922UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAMay 27, 2015abuse@upcloud.com
└ 80.69.172.0/23512SIGMATIC-1UpCloud Cloud ServersASSIGNED PAMay 27, 2015abuse@upcloud.com
via FI-UPCLOUD-20090922
└ 80.69.174.0/23512SIGMATIC-1UpCloud Cloud ServersASSIGNED PAMay 27, 2015abuse@upcloud.com
via FI-UPCLOUD-20090922

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 2015
Current origin since
Apr 2015 · 12 yr
Origin networks
1