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

95.68.252.0/24

8 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
48
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • Kookey
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.68.128.0/1732,768RU-RTK-20081113PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 13, 2008abuse@rt.ru
└ 95.68.251.0 - 95.68.252.255512ULVT-NETRostelecomASSIGNED PAOct 21, 2025abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced 95.68.128.0/17

95.68.128.0/17

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Apr 2016 · 11 yr
Origin networks
2
Last change of origin
Apr 2016
Recorded history

History

Handoffs
1