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

212.20.0.0/18

1 anonymizer address · <0.01% · VPN272 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
272
1.7% of its addresses · 30 days
Always-on exits
34
13% of its exits
Spread
30 of 64
/24s with at least one exit
Providers
121
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

110K observations
  • VPN · anonymizer
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
212.20.46.0/24418
212.20.43.0/24417
212.20.49.0/24415
212.20.53.0/24317
212.20.52.0/24317
212.20.50.0/24219
212.20.45.0/24217
212.20.54.0/24215
212.20.47.0/24214
212.20.42.0/24212
212.20.44.0/24120
212.20.48.0/24118
212.20.51.0/24116
212.20.41.0/24110
212.20.1.0/2412
212.20.3.0/2412
212.20.40.0/24015
212.20.15.0/2408
212.20.2.0/2403
212.20.62.0/2402
212.20.18.0/2402
212.20.58.0/2402
212.20.55.0/2402
212.20.23.0/2402

Proxy providers listing exits

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

Path

1 · Holder
PJSC Rostelecom
record created Feb 28, 2002
2 · Leased from
not leased
3 · Announced by
AS12389 PJSC Rostelecom
since Aug 2016 · 10.2 yr ago
4 · Use
VPN servicesnamed VPN Gate
Residential

Operators, sellers and brokers

VPN services

NameParentIn 212.20.0.0/18/24s
VPN GateUniversity of Tsukuba
1<0.01%
1

Lineage

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

212.20.0.0/18

From the registry to its use

  1. Feb 28, 2002
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    212.20.0.0/18
  2. May 9, 2005– Dec 22, 2010
    Announced
    AS8691
  3. Jan 1, 2011– Jun 27, 2016
    Announced
    AS41440 PJSC Rostelecom
  4. Aug 15, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  5. Oct 30, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  6. today
    Used
    VPN Gate
    VPN

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
212.20.4.0/22
since Aug 2016
AS12389ResidentialPJSC Rostelecom
212.20.8.0/22
since Aug 2016
AS12389ResidentialPJSC Rostelecom
212.20.36.0/22
since Aug 2016
AS12389ResidentialPJSC 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
212.20.0.0/1816,384RU-RTK-980220PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 28, 2002abuse@rt.ru
└ 212.20.0.0/24256RINET-TURBOOJSC SibirtelecomASSIGNED PAOct 25, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.1.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.0/24256RU-RTK-980220unknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.0/25128RINET-TURBORINET-TURBO officeASSIGNED PAOct 14, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.128/2664RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.2.192/2664RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.3.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.4.0 - 212.20.12.2552,304WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.13.0/24256DEFIS-NETDefis ltd.ASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.14.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PADec 23, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.15.0/24256SIBACC-NET"Siberian Accord"ASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.16.0/24256RU-RTK-980220unknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-980220
└ 212.20.17.0/24256GORSKAYA-NETGORSKAYA JSC off 609ASSIGNED PAOct 14, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.18.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.19.0/24256RCINSKCentral Bank of RussiaASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.20.0/23512WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.22.32/298RISP-SANCSibAncorASSIGNED PAMar 16, 2004abuse@rt.ru
via RU-RTK-980220
└ 212.20.22.40/298RISP-SRBRFFPThe Siberian Inter-Regional BranchASSIGNED PAMar 17, 2004abuse@rt.ru
via RU-RTK-980220
└ 212.20.23.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.24.0/24256FIS-NETWORKFinancial Information ServiceASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.25.0/24256GORKOGO-NETGORKOGO, 51, Novosibirsk, RUASSIGNED PAMay 24, 2007abuse@rt.ru
via RU-RTK-980220
└ 212.20.27.0/24256OLYMPIA-REISENOlympia-Reisen-Sibir Close CorporationASSIGNED PA—abuse@rt.ru
via RU-RTK-980220
└ 212.20.28.0/23512WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.30.0/24256RINET-TURBOOJSC SibirtelecomASSIGNED PAOct 25, 2010abuse@rt.ru
via RU-RTK-980220
└ 212.20.31.0 - 212.20.33.255768WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.34.0/298RISP-TSIJSC TrustServiceInvestASSIGNED PADec 25, 2003abuse@rt.ru
via RU-RTK-980220
└ 212.20.34.48/2816RISP-TSIRosSelhozBankASSIGNED PADec 25, 2003abuse@rt.ru
via RU-RTK-980220
└ 212.20.34.64/2732RISP-TSIJSC "Sibirskoe Obshestvo"ASSIGNED PADec 25, 2003abuse@rt.ru
via RU-RTK-980220
└ 212.20.35.0/24256WEBSTREAMclients NSK RT static poolASSIGNED PAJan 27, 2012abuse@rt.ru
via RU-RTK-980220
└ 212.20.36.0 - 212.20.59.2556,144WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAJul 19, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.60.0/2732NGONBNovosibirsk State Regional Academic LibraryASSIGNED PAJul 19, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.60.128/2664eseti-nskCJSC RESASSIGNED PASep 12, 2011abuse@rt.ru
via RU-RTK-980220
└ 212.20.62.0/23512CONTENT-CENTEROJSC "Sibirtelecom"ASSIGNED PAJan 14, 2011abuse@rt.ru
via RU-RTK-980220

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
Residential15,95997%14
Business4242.6%10
VPNanonymizer1<0.01%1

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2016 · 10 yr
Origin networks
3
Last change of origin
Aug 2016
Recorded history

History

Handoffs
2