Data as of Nov 15, 2026

95.111.208.0/22

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

Exits seen per day

266 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.111.208.0/2402
95.111.209.0/2402
95.111.211.0/2402

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • GSocks
  • HideProxy
  • Infatica
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • Q2IP
  • RainProxy
  • SPYDERPROXY_BASIC
  • 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
95.111.192.0/198,192FI-UPCLOUD-20081230UpCloud Ltd (ORG-UL87-RIPE) · FIALLOCATED PAMay 12, 2020abuse@upcloud.com
└ 95.111.208.0/221,024UPCLOUD-SE-STO1-NETunknownASSIGNED PASep 5, 2023abuse@upcloud.com
via FI-UPCLOUD-20081230

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
Jun 2022
Current origin since
Jun 2022 · 4.4 yr
Origin networks
1