Data as of Nov 18, 2026

212.164.0.0/16

5 anonymizer addresses · <0.01% · VPN7,815 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
7,815
12% of its addresses · 30 days
Always-on exits
2,170
28% of its exits
Spread
135 of 256
/24s with at least one exit
Providers
163
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

6.1M observations
  • VPN · anonymizer
  • Residential

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_BASIC
  • AETHYN_ELITE
  • APROXY
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BUYPERSONALPROXY
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • FuseProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IP2WORLD
  • IPCola
  • IPFly
  • IPMUSK
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LAMAPROXY
  • LITPORT_LIMA
  • LOKIPROXY
  • LUMIPROXY
  • LemonBright
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • Maskify
  • MoMoProxy
  • NSTPROXY_LITE
  • NSTPROXY_PRIME
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXIES.RIP
  • PROXIWARE_ECO
  • PROXORA
  • PROXYCOVE
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSALE
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PROXY_CC
  • PSBProxy
  • PYPROXY
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • RoamProxy
  • RolaProxy
  • SIMPLYNODE
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM
IPv4 market

Path

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

Operators, sellers and brokers

VPN services

NameParentIn 212.164.0.0/16/24s
VPN GateUniversity of Tsukuba
5<0.01%
5

Lineage

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

212.164.0.0/16

From the registry to its use

  1. Feb 28, 2002
    Registry record
    PJSC Rostelecom
    ALLOCATED PA
    212.164.0.0/16
  2. May 9, 2005– Dec 22, 2010
    Announced
    AS8691 Unregistered ASN
  3. Jan 1, 2011– Jun 27, 2016
    Announced
    AS41440 PJSC Rostelecom
  4. Aug 15, 2016– today
    Announced
    AS12389 PJSC Rostelecom
    Internet provider
  5. Sep 27, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
  6. Oct 25, 2018
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
    212.164.176.0/22
  7. Jun 21, 2025
    Route object
    AS12389 PJSC Rostelecom
    RIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
    212.164.24.0/21
  8. today
    Used
    VPN Gate
    VPN

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

Arrived
PrefixOriginTypeAnonymizer addressesOperatorProxy exitsHolderRPKI
212.164.0.0/20
since Aug 2016
AS12389Residential992PJSC Rostelecom
212.164.16.0/21
since Apr 2021
AS12389ResidentialPJSC Rostelecom
212.164.24.0/23
since Aug 2025
AS12389Residential506
334 always on
PJSC Rostelecom
212.164.24.0/24
since Aug 2025
AS12389Residential254
163 always on
PJSC Rostelecom
212.164.25.0/24
since Aug 2025
AS12389Residential252
171 always on
PJSC Rostelecom
212.164.26.0/23
since Aug 2025
AS12389Residential510
328 always on
PJSC Rostelecom
212.164.26.0/24
since Aug 2025
AS12389Residential255
168 always on
PJSC Rostelecom
212.164.27.0/24
since Aug 2025
AS12389Residential255
160 always on
PJSC Rostelecom
212.164.28.0/23
since Oct 2025
AS12389Residential511
149 always on
PJSC Rostelecom
212.164.28.0/24
since Oct 2025
AS12389Residential10.39%VPNVPN servicesoperated by VPN Gate255
76 always on
PJSC Rostelecom
212.164.29.0/24
since Oct 2025
AS12389Residential256
73 always on
PJSC Rostelecom
212.164.30.0/23
since Aug 2025
AS12389Residential511
60 always on
PJSC Rostelecom
212.164.30.0/24
since Aug 2025
AS12389Residential255
29 always on
PJSC Rostelecom
212.164.31.0/24
since Aug 2025
AS12389Residential256
31 always on
PJSC Rostelecom
212.164.32.0/22
since Aug 2016
AS12389Residential272PJSC Rostelecom
212.164.38.0/23
since Sep 2017
AS12389Residential503
415 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.38.0/24
since May 2018
AS12389Residential249
201 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.39.0/24
since May 2018
AS12389Residential10.39%VPNVPN servicesoperated by VPN Gate254
214 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.40.0/21
since Mar 2024
AS12389Residential523PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.64.0/23
since Sep 2017
AS12389Residential504
394 always on
PJSC Rostelecom
212.164.64.0/24
since May 2018
AS12389Residential252
200 always on
PJSC Rostelecom
212.164.65.0/24
since May 2018
AS12389Residential252
194 always on
PJSC Rostelecom
212.164.80.0/22
since Mar 2024
AS12389Residential149PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.88.0/21
since May 2021
AS12389ResidentialPJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.96.0/23
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.96.0/24
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.97.0/24
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.98.0/23
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.98.0/24
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.99.0/24
since Sep 2020
AS12389ResidentialPJSC Rostelecom
212.164.112.0/20
since Aug 2016
AS12389Residential20.05%VPNVPN servicesoperated by VPN Gate97
18 always on
PJSC Rostelecom
212.164.128.0/19
since Oct 2019
AS12389Residential1PJSC Rostelecom
212.164.128.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
212.164.129.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
212.164.130.0/24
since Mar 2024
AS12389ResidentialPJSC Rostelecom
212.164.131.0/24
since Jan 2020
AS12389ResidentialPJSC Rostelecom
212.164.132.0/23
since Apr 2020
AS12389ResidentialPJSC Rostelecom
212.164.136.0/21
since Mar 2024
AS12389Residential1PJSC Rostelecom
212.164.160.0/20
since Jun 2018
AS12389Residential1,081
1 always on
PJSC Rostelecom
212.164.176.0/23
since Aug 2025
AS12389ResidentialPJSC Rostelecom
212.164.178.0/23
since Sep 2025
AS12389Residential504
450 always on
PJSC Rostelecom
212.164.178.0/24
since Sep 2025
AS12389Residential255
223 always on
PJSC Rostelecom
212.164.179.0/24
since Sep 2025
AS12389Residential249
227 always on
PJSC Rostelecom
212.164.184.0/21
since Aug 2016
AS12389Residential503PJSC Rostelecom
212.164.196.0/22
since Aug 2016
AS12389Residential185PJSC Rostelecom
212.164.204.0/24
since Oct 2019
AS12389ResidentialPJSC Rostelecom
212.164.205.0/24
since Oct 2019
AS12389ResidentialPJSC Rostelecom
212.164.206.0/24
since Nov 2019
AS12389Residential121PJSC Rostelecom
212.164.207.0/24
since Nov 2019
AS12389Residential117PJSC Rostelecom
212.164.208.0/20
since Aug 2016
AS12389Residential10.02%VPNVPN servicesoperated by VPN Gate44
6 always on
PJSC Rostelecom
212.164.224.0/21
since Aug 2016
AS12389Residential18
1 always on
PJSC Rostelecom
212.164.232.0/21
since Aug 2016
AS12389Residential19
3 always on
PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.240.0/22
since Mar 2025
AS12389Residential1PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.244.0/24
since Apr 2020
AS12389Residential20PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.245.0/24
since Apr 2020
AS12389Residential21PJSC Rostelecom
via OJSC "Sibirtelecom"
212.164.252.0/22
since Mar 2025
AS12389Residential9
2 always on
PJSC 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.164.0.0/1665,536RU-RTK-19981215PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 28, 2002abuse@rt.ru
└ 212.164.0.0/24256RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PASep 21, 2006abuse@rt.ru
via RU-RTK-19981215
└ 212.164.1.0 - 212.164.13.2553,328WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 26, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.14.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.15.0 - 212.164.35.2555,376WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 26, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.36.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.37.0 - 212.164.55.2554,864WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-19981215
└ 212.164.48.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.49.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.50.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.51.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.52.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.53.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.54.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.55.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.56.0 - 212.164.58.255768WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.59.0 - 212.164.63.2551,280WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.64.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.65.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.66.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.67.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.68.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.69.0/24256ASDG-NETASDGASSIGNED PA—abuse@rt.ru
via RU-RTK-19981215
└ 212.164.70.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.71.0/24256RINET-TURBOOJSC RINet, Novosibirsk, RussiaASSIGNED PAMay 7, 2007abuse@rt.ru
via RU-RTK-19981215
└ 212.164.72.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.73.0 - 212.164.79.2551,792WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PANov 2, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.80.0/204,096WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-19981215
└ 212.164.80.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.81.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.82.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.83.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.84.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.85.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.86.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.87.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.96.0 - 212.164.98.255768WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.99.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.100.0/23512WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.102.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.103.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.104.0 - 212.164.109.2551,536WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.110.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.111.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.112.0/204,096WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 26, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.128.0/198,192Soc_TelcoPJSC "Rostelecom"ASSIGNED PAOct 26, 2010abuse@rt.ru
└ 212.164.160.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.161.0 - 212.164.175.2553,840WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 26, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.176.0/221,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.180.0 - 212.164.182.255768WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.183.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.184.0/212,048WEBSTREAMOJSC "Rostelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.192.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.193.0 - 212.164.194.255512WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.195.0 - 212.164.198.2551,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.199.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.200.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.201.0/24256SINETICSinetic LtdASSIGNED PA—abuse@rt.ru
via RU-RTK-19981215
└ 212.164.202.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.203.0 - 212.164.207.2551,280WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.208.0/204,096WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.224.0/24256WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.225.0 - 212.164.249.2556,400WEBSTREAMOJSC "Sibirtelecom"SUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-19981215
└ 212.164.240.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.241.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.242.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.243.0/24256WEBSTREAMunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via WEBSTREAM
└ 212.164.250.0/23512WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215
└ 212.164.252.0/221,024WEBSTREAMOJSC "Sibirtelecom"ASSIGNED PAOct 28, 2010abuse@rt.ru
via RU-RTK-19981215

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

65,536 addresses
TypeAddressesShareRanges
Residential65,531>99%62
VPNanonymizer5<0.01%5

Network & registry

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