Data as of Nov 10, 2026

178.185.0.0/17

1 anonymizer address · <0.01% · VPN5,374 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
5,374
16% of its addresses · 30 days
Spread
128 of 128
/24s with at least one exit
Providers
118
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

399K observations
  • VPN · anonymizer
  • Residential

Proxy providers listing exits

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

Path

1 · Holder
record created Feb 3, 2010 · reallocated to a party the registry does not name Feb 10, 2010
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Mar 2016 · 10.6 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 178.185.0.0/17/24s
VPN GateUniversity of Tsukuba
1<0.01%
1

Lineage

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

178.185.0.0/17

From the registry to its use

  1. Feb 3, 2010
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    178.184.0.0/14
  2. Apr 15, 2010– Mar 15, 2016
    Announced
    AS41440 PJSC Rostelecom
  3. Mar 22, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  4. Sep 10, 2018– today
    Announced
    AS12389 PJSC Rostelecom
    as part of 178.184.0.0/14
    178.184.0.0/14
  5. Nov 6, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  6. today
    Used
    VPN Gate
    VPN

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.184.0.0/14
since Sep 2018
AS12389Residential49,789
58 always on
PJSC Rostelecom
More specific

Announcements inside

PrefixOriginTypeAnonymizer addressesOperatorProxy exitsHolderRPKI
178.185.0.0/18
since Mar 2016
AS12389Residential1<0.01%VPNVPN servicesoperated by VPN Gate2,709PJSC Rostelecom
178.185.64.0/18
since Mar 2016
AS12389Residential2,688PJSC 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
178.184.0.0/14262,144RU-RTK-20100203PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 3, 2010abuse@rt.ru
└ 178.185.0.0/1665,536Rostelecom_netJSC Rostelecom . Korporativniy Centr.LIR-PARTITIONED PANov 2, 2010abuse@rt.ru
via RU-RTK-20100203
└ 178.185.0.0/1732,768RU-SIBNETunknownLIR-PARTITIONED PAFeb 10, 2010abuse@rt.ru
via Rostelecom_net
└ 178.185.0.0/1816,384WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAApr 21, 2010abuse@rt.ru
via RU-SIBNET
└ 178.185.64.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJun 9, 2010abuse@rt.ru
via RU-SIBNET
└ 178.185.96.0/198,192WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJul 14, 2010abuse@rt.ru
via RU-SIBNET

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

32,768 addresses
TypeAddressesShareRanges
Residential32,767>99%3
VPNanonymizer1<0.01%1

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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

History

Handoffs
1