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

95.111.192.0/21

9 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
9
0.44% of its addresses · 30 days
Spread
5 of 8
/24s with at least one exit
Providers
23
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

291 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.111.192.0/2404
95.111.193.0/2401
95.111.195.0/2401
95.111.196.0/2401
95.111.198.0/2401

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • GSocks
  • GloryCloud
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

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.192.0/221,024UPCLOUD-SG-SIN1-NETunknownASSIGNED PAMay 13, 2020abuse@upcloud.com
via FI-UPCLOUD-20081230
└ 95.111.196.0/221,024UPCLOUD-SG-SIN1-NETunknownASSIGNED PAMay 13, 2020abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2012
Current origin since
Jan 2025 · 1.8 yr
Origin networks
2
Last change of origin
May 2020
Recorded history

History

Handoffs
1