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

95.70.64.0/18

2 anonymizer addresses · 0.01% · VPN3,971 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
AS12389
Type
Residential
>99% of it

Residential-proxy exits

Proxy exits
3,971
24% of its addresses · 30 days
Always-on exits
46
1.2% of its exits
Spread
64 of 64
/24s with at least one exit
Providers
109
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

260K observations
  • VPN · anonymizer
  • Residential

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.70.89.0/24271
95.70.81.0/24270
95.70.107.0/24262
95.70.125.0/24259
95.70.77.0/24259
95.70.127.0/24258
95.70.67.0/24257
95.70.121.0/24252
95.70.94.0/24182
95.70.99.0/24181
95.70.112.0/24178
95.70.119.0/24175
95.70.65.0/24173
95.70.98.0/24173
95.70.124.0/24172
95.70.122.0/24169
95.70.120.0/24169
95.70.72.0/24167
95.70.96.0/24166
95.70.76.0/24166
95.70.126.0/24166
95.70.117.0/24164
95.70.84.0/24163
95.70.87.0/24162

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • HydraProxy
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • Maskify
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RealProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

1 · Holder
PJSC Rostelecom
record created Nov 21, 2008
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Jun 2016 · 10.4 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 95.70.64.0/18/24s
VPN GateUniversity of Tsukuba
20.01%
2

Lineage

How this block came to its use, oldest first. The whole IPv4 market →

95.70.64.0/18

From the registry to its use

  1. Nov 21, 2008
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    95.70.0.0/17
  2. Feb 8, 2010– Apr 22, 2015
    Announced
    AS34584 PJSC Rostelecom
    Internet provider
  3. Jun 15, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  4. Oct 25, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  5. today
    Used
    VPN Gate
    VPN

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.70.0.0/1732,768RU-RTK-20081121PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 21, 2008abuse@rt.ru
└ 95.70.64.0/221,024KHT-XDSLPppoE pool for xDSL links in Birobidjan town, cetnral node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.68.0/221,024KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, ats-718 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.72.0/221,024KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, ats-718 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.76.0/221,024KHT-XDSLPppoE pool for xDSL links in Birobidjan town, cetnral node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.80.0/204,096KHT-XDSLPppoE pool for xDSL links in Komsomolsk-at-Amur town, ats-220 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.96.0/212,048KHT-XDSLPppoE pool for xDSL links in Komsomolsk-at-Amur town, central node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.104.0/212,048KHT-XDSLPppoE pool for xDSL links in Birobidjan town, central node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.112.0/221,024KHT-XDSLPppoE pool for xDSL links in Sovietskaya Gavan town, cetnral node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.116.0/221,024KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, ats-21 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.120.0/221,024KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, ats-51 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.124.0/23512KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, central node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121
└ 95.70.126.0/24256KHT-XDSLPppoE pool for xDSL links in Khabarovsk city, ats-718 node BRASASSIGNED PADec 21, 2010abuse@rt.ru
via RU-RTK-20081121

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

16,384 addresses
TypeAddressesShareRanges
Residential16,382>99%3
VPNanonymizer20.01%2

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Feb 2010
Current origin since
Jun 2016 · 10 yr
Origin networks
2
Last change of origin
Jun 2016
Recorded history

History

Handoffs
1