Data as of Nov 16, 2026

95.128.160.0/22

40 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
40
3.9% of its addresses · 30 days
Always-on exits
1
2.5% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
51
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

2.0K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • AETHYN_ELITE
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GhostConnect
  • HASDATA
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • 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.128.160.0/212,048RU-RTK-20090130PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 14, 2022abuse@rt.ru
└ 95.128.160.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAMar 30, 2015abuse@rt.ru
via RU-RTK-20090130
└ 95.128.161.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAMar 30, 2015abuse@rt.ru
via RU-RTK-20090130
└ 95.128.162.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAMar 30, 2015abuse@rt.ru
via RU-RTK-20090130
└ 95.128.163.0/24256AISTNETAIST ISP, PPTP (physical persons)ASSIGNED PAMar 30, 2015abuse@rt.ru
via RU-RTK-20090130

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
Feb 2013
Current origin since
Feb 2013 · 14 yr
Origin networks
1