Data as of Nov 12, 2026

95.170.239.0/24

3 residential-proxy exits · 30 days

RUPKKI s.r.o.

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Sep 2026
from AS16006 RUPKKI s.r.o., after 5.8 years unannounced

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
25
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

467 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • ThunderProxy
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.170.224.0/19
since Nov 2020
AS16006Residential142
23 always on
RUPKKI s.r.o.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.170.224.0/198,192SK-SK-RUP-20090206RUPKKI s.r.o. (ORG-RS27-RIPE) · SKALLOCATED PAFeb 6, 2009abuse@rupkki.sk
└ 95.170.225.0 - 95.170.247.2555,888RUPKKI-CUST-RESIDENTALRUPKKI s.r.o., residential customersASSIGNED PAJun 28, 2011abuse@rupkki.sk
via SK-SK-RUP-20090206

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

Covering aggregate above, the prefix's own history below

95.170.236.0/22

Routing history

Pattern
Stable
First seen
Feb 2013
Current origin since
Sep 2026 · 2 mo
Origin networks
1