Data as of Nov 16, 2026

95.54.138.0/24

37 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
37
14% of its addresses · 30 days
Always-on exits
1
2.7% of its exits
Providers
72
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

3.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SOTAPROXY
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.52.0.0/14
since Sep 2018
AS12389Residential32,779
1,200 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.52.0.0/14262,144RU-RTK-20081113PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 13, 2008abuse@rt.ru
└ 95.54.128.0/198,192RU-AVANGARD-DSLOJSC "North-West Telecom"ASSIGNED PASep 22, 2009abuse@rt.ru
via RU-RTK-20081113

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.54.128.0/17

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Jul 2017 · 9.3 yr
Origin networks
2
Last change of origin
Jul 2017
Recorded history

History

Handoffs
1