Data as of Nov 18, 2026
212.164.0.0/16
5 anonymizer addresses · <0.01% · VPN7,815 residential-proxy exits · 30 daysPJSC Rostelecom
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
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.164.179.0/24 | 227 | 249 | |
| 212.164.178.0/24 | 223 | 255 | |
| 212.164.39.0/24 | 214 | 254 | |
| 212.164.38.0/24 | 201 | 249 | |
| 212.164.64.0/24 | 200 | 252 | |
| 212.164.65.0/24 | 194 | 252 | |
| 212.164.25.0/24 | 171 | 252 | |
| 212.164.26.0/24 | 168 | 255 | |
| 212.164.24.0/24 | 163 | 254 | |
| 212.164.27.0/24 | 160 | 255 | |
| 212.164.28.0/24 | 76 | 255 | |
| 212.164.29.0/24 | 73 | 256 | |
| 212.164.31.0/24 | 31 | 256 | |
| 212.164.30.0/24 | 29 | 255 | |
| 212.164.116.0/24 | 8 | 23 | |
| 212.164.115.0/24 | 4 | 17 | |
| 212.164.246.0/24 | 3 | 25 | |
| 212.164.118.0/24 | 3 | 20 | |
| 212.164.113.0/24 | 2 | 13 | |
| 212.164.219.0/24 | 2 | 5 | |
| 212.164.63.0/24 | 2 | 3 | |
| 212.164.165.0/24 | 1 | 71 | |
| 212.164.222.0/24 | 1 | 6 | |
| 212.164.215.0/24 | 1 | 5 |
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
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 212.164.0.0/16 | /24s |
|---|---|---|---|
| VPN Gate | University 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
- Feb 28, 2002Registry recordPJSC RostelecomALLOCATED PA212.164.0.0/16
- May 9, 2005– Dec 22, 2010AnnouncedAS8691 Unregistered ASN
- Jan 1, 2011– Jun 27, 2016AnnouncedAS41440 PJSC Rostelecom
- Aug 15, 2016– today
- Sep 27, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- Oct 25, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT212.164.176.0/22
- Jun 21, 2025Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT212.164.24.0/21
- todayUsedVPN GateVPN
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
| Prefix | Origin | Type | Anonymizer addresses | Operator | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|---|---|
| 212.164.0.0/20 since Aug 2016 | AS12389 | Residential | 992 | PJSC Rostelecom | |||
| 212.164.16.0/21 since Apr 2021 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.24.0/23 since Aug 2025 | AS12389 | Residential | 506 334 always on | PJSC Rostelecom | |||
| 212.164.24.0/24 since Aug 2025 | AS12389 | Residential | 254 163 always on | PJSC Rostelecom | |||
| 212.164.25.0/24 since Aug 2025 | AS12389 | Residential | 252 171 always on | PJSC Rostelecom | |||
| 212.164.26.0/23 since Aug 2025 | AS12389 | Residential | 510 328 always on | PJSC Rostelecom | |||
| 212.164.26.0/24 since Aug 2025 | AS12389 | Residential | 255 168 always on | PJSC Rostelecom | |||
| 212.164.27.0/24 since Aug 2025 | AS12389 | Residential | 255 160 always on | PJSC Rostelecom | |||
| 212.164.28.0/23 since Oct 2025 | AS12389 | Residential | 511 149 always on | PJSC Rostelecom | |||
| 212.164.28.0/24 since Oct 2025 | AS12389 | Residential | 10.39%VPN | VPN servicesoperated by VPN Gate | 255 76 always on | PJSC Rostelecom | |
| 212.164.29.0/24 since Oct 2025 | AS12389 | Residential | 256 73 always on | PJSC Rostelecom | |||
| 212.164.30.0/23 since Aug 2025 | AS12389 | Residential | 511 60 always on | PJSC Rostelecom | |||
| 212.164.30.0/24 since Aug 2025 | AS12389 | Residential | 255 29 always on | PJSC Rostelecom | |||
| 212.164.31.0/24 since Aug 2025 | AS12389 | Residential | 256 31 always on | PJSC Rostelecom | |||
| 212.164.32.0/22 since Aug 2016 | AS12389 | Residential | 272 | PJSC Rostelecom | |||
| 212.164.38.0/23 since Sep 2017 | AS12389 | Residential | 503 415 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.38.0/24 since May 2018 | AS12389 | Residential | 249 201 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.39.0/24 since May 2018 | AS12389 | Residential | 10.39%VPN | VPN servicesoperated by VPN Gate | 254 214 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |
| 212.164.40.0/21 since Mar 2024 | AS12389 | Residential | 523 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.64.0/23 since Sep 2017 | AS12389 | Residential | 504 394 always on | PJSC Rostelecom | |||
| 212.164.64.0/24 since May 2018 | AS12389 | Residential | 252 200 always on | PJSC Rostelecom | |||
| 212.164.65.0/24 since May 2018 | AS12389 | Residential | 252 194 always on | PJSC Rostelecom | |||
| 212.164.80.0/22 since Mar 2024 | AS12389 | Residential | 149 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.88.0/21 since May 2021 | AS12389 | Residential | PJSC Rostelecom via OJSC "Sibirtelecom" | ||||
| 212.164.96.0/23 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.96.0/24 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.97.0/24 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.98.0/23 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.98.0/24 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.99.0/24 since Sep 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.112.0/20 since Aug 2016 | AS12389 | Residential | 20.05%VPN | VPN servicesoperated by VPN Gate | 97 18 always on | PJSC Rostelecom | |
| 212.164.128.0/19 since Oct 2019 | AS12389 | Residential | 1 | PJSC Rostelecom | |||
| 212.164.128.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.129.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.130.0/24 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.131.0/24 since Jan 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.132.0/23 since Apr 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.136.0/21 since Mar 2024 | AS12389 | Residential | 1 | PJSC Rostelecom | |||
| 212.164.160.0/20 since Jun 2018 | AS12389 | Residential | 1,081 1 always on | PJSC Rostelecom | |||
| 212.164.176.0/23 since Aug 2025 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.178.0/23 since Sep 2025 | AS12389 | Residential | 504 450 always on | PJSC Rostelecom | |||
| 212.164.178.0/24 since Sep 2025 | AS12389 | Residential | 255 223 always on | PJSC Rostelecom | |||
| 212.164.179.0/24 since Sep 2025 | AS12389 | Residential | 249 227 always on | PJSC Rostelecom | |||
| 212.164.184.0/21 since Aug 2016 | AS12389 | Residential | 503 | PJSC Rostelecom | |||
| 212.164.196.0/22 since Aug 2016 | AS12389 | Residential | 185 | PJSC Rostelecom | |||
| 212.164.204.0/24 since Oct 2019 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.205.0/24 since Oct 2019 | AS12389 | Residential | PJSC Rostelecom | ||||
| 212.164.206.0/24 since Nov 2019 | AS12389 | Residential | 121 | PJSC Rostelecom | |||
| 212.164.207.0/24 since Nov 2019 | AS12389 | Residential | 117 | PJSC Rostelecom | |||
| 212.164.208.0/20 since Aug 2016 | AS12389 | Residential | 10.02%VPN | VPN servicesoperated by VPN Gate | 44 6 always on | PJSC Rostelecom | |
| 212.164.224.0/21 since Aug 2016 | AS12389 | Residential | 18 1 always on | PJSC Rostelecom | |||
| 212.164.232.0/21 since Aug 2016 | AS12389 | Residential | 19 3 always on | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.240.0/22 since Mar 2025 | AS12389 | Residential | 1 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.244.0/24 since Apr 2020 | AS12389 | Residential | 20 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.245.0/24 since Apr 2020 | AS12389 | Residential | 21 | PJSC Rostelecom via OJSC "Sibirtelecom" | |||
| 212.164.252.0/22 since Mar 2025 | AS12389 | Residential | 9 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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 212.164.0.0/16 | 65,536 | RU-RTK-19981215 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Feb 28, 2002 | abuse@ |
| └ 212.164.0.0/24 | 256 | RINET-TURBO | OJSC RINet, Novosibirsk, Russia | ASSIGNED PA | Sep 21, 2006 | abuse@ via RU-RTK-19981215 |
| └ 212. | 3,328 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 26, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.14.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 5,376 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 26, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.36.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 4,864 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via RU-RTK-19981215 |
| └ 212.164.48.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.49.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.50.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.51.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.52.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.53.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.54.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.55.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212. | 768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 1,280 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.64.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.65.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.66.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.67.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.68.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.69.0/24 | 256 | ASDG-NET | ASDG | ASSIGNED PA | — | abuse@ via RU-RTK-19981215 |
| └ 212.164.70.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.71.0/24 | 256 | RINET-TURBO | OJSC RINet, Novosibirsk, Russia | ASSIGNED PA | May 7, 2007 | abuse@ via RU-RTK-19981215 |
| └ 212.164.72.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 1,792 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 2, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.80.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via RU-RTK-19981215 |
| └ 212.164.80.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.81.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.82.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.83.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.84.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.85.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.86.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.87.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212. | 768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.99.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.100.0/23 | 512 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.102.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.103.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 1,536 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.110.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.111.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.112.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 26, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.128.0/19 | 8,192 | Soc_ | PJSC "Rostelecom" | ASSIGNED PA | Oct 26, 2010 | abuse@ |
| └ 212.164.160.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 3,840 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 26, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.176.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.183.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.184.0/21 | 2,048 | WEBSTREAM | OJSC "Rostelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.192.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 512 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.199.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.200.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.201.0/24 | 256 | SINETIC | Sinetic Ltd | ASSIGNED PA | — | abuse@ via RU-RTK-19981215 |
| └ 212.164.202.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 1,280 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.208.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.224.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212. | 6,400 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via RU-RTK-19981215 |
| └ 212.164.240.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.241.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.242.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.243.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 212.164.250.0/23 | 512 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-19981215 |
| └ 212.164.252.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ 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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 65,531 | >99% | 62 | |
| VPNanonymizer | 5 | <0.01% | 5 |
Network & registry
Origin network
AS12389
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Jul 1, 2005
- Domain
- rt.ru
- Website
- www.company.rt.ru/en/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
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
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.164.0.0/16 | AS12389 | /24 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Sep 27, 2018 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 212.164.24.0/21 | AS12389 | RIPE | ROSTELECOM-MNT | Jun 21, 2025 | |
| 212.164.176.0/22 | AS12389 | RIPE | Rostelecom networks | ROSTELECOM-MNT | Oct 25, 2018 |
Whois
Registration for this announcement
- Range
- 212.
164. 0. 0/ 16 - Netname
- RU-RTK-19981215
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Feb 28, 2002
- Updated
- Jun 4, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 15, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE