Data as of Nov 20, 2026

95.156.126.0/24

5 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
5
2.0% of its addresses · 30 days
Always-on exits
2
40% of its exits
Providers
42
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

20K observations

Proxy providers listing exits

  • AETHYN_BASIC
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • IPFly
  • IPRoyal
  • Infatica
  • KindProxy
  • LOKIPROXY
  • MangoProxy
  • Maskify
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.156.64.0/18
since Dec 2016
AS12389Residential269
10 always on
PJSC Rostelecom

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.156.64.0/1816,384RU-RTK-20090318PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAMar 18, 2009abuse@rt.ru
└ 95.156.112.0/204,096KRASLANJSC Rostelecom LIRASSIGNED PAOct 14, 2025abuse@rt.ru
via RU-RTK-20090318

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

Summary

Routing history

Pattern
Stable
First seen
Mar 2025
Current origin since
Mar 2025 · 1.7 yr
Origin networks
1