Data as of Nov 15, 2026

81.27.96.0/22

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

Exits seen per day

790 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
81.27.97.0/2407
81.27.96.0/2403
81.27.98.0/2401
81.27.99.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HideProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • 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
81.27.96.0/204,096FI-UPCLOUD-20020411UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAJun 16, 2025abuse@upcloud.com
└ 81.27.96.0/221,024UPCLOUD-FI-HEL2-NETUpCloud Cloud ServersASSIGNED PAOct 15, 2025abuse@upcloud.com
via FI-UPCLOUD-20020411

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
Oct 2025
Current origin since
Oct 2025 · 1.1 yr
Origin networks
1