Data as of Nov 9, 2026
92.124.0.0/14
5 anonymizer addresses · <0.01% · VPNPJSC Rostelecom
Residential-proxy exits
Proxy exits
21,395
8.2% of its addresses · listed by providers
Always-on exits
1,402
6.6% of its exits
Spread
600 of 1,024
/24s with at least one exit
Providers
128
selling exits here
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 92.124.162.0/24 | 173 | 255 | |
| 92.124.160.0/24 | 169 | 255 | |
| 92.124.163.0/24 | 163 | 256 | |
| 92.124.161.0/24 | 157 | 254 | |
| 92.126.118.0/24 | 73 | 256 | |
| 92.126.117.0/24 | 69 | 256 | |
| 92.126.119.0/24 | 62 | 256 | |
| 92.126.116.0/24 | 44 | 256 | |
| 92.124.204.0/24 | 28 | 255 | |
| 92.124.205.0/24 | 21 | 256 | |
| 92.124.207.0/24 | 20 | 256 | |
| 92.124.206.0/24 | 19 | 256 | |
| 92.126.60.0/24 | 8 | 34 | |
| 92.126.23.0/24 | 8 | 33 | |
| 92.124.147.0/24 | 7 | 17 | |
| 92.126.11.0/24 | 6 | 41 | |
| 92.126.57.0/24 | 6 | 40 | |
| 92.126.16.0/24 | 6 | 38 | |
| 92.126.50.0/24 | 6 | 31 | |
| 92.124.131.0/24 | 6 | 28 | |
| 92.125.44.0/24 | 5 | 42 | |
| 92.126.54.0/24 | 5 | 40 | |
| 92.126.34.0/24 | 5 | 37 | |
| 92.126.52.0/24 | 5 | 36 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- JoyProxy
- KindProxy
- KocerRoxy
- Kookey
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- 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
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- 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 92.124.0.0/14 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 5<0.01% | 5 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
92.124.0.0/14
From the registry to its use
- May 22, 2008Registry recordPJSC RostelecomALLOCATED PA92.124.0.0/14
- Mar 22, 2009– Jun 15, 2016AnnouncedAS41440 PJSC Rostelecom
- Jun 22, 2016– Jun 27, 2016
- Aug 15, 2016– today
- Sep 20, 2018Route objectAS12389 PJSC RostelecomRIPE route object for AS12389 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- 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 |
|---|---|---|---|---|---|---|---|
| 92.124.0.0/18 since Jul 2015 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.124.64.0/18 since Jun 2019 | AS12389 | Residential | 20.01%VPN | VPN servicesoperated by VPN Gate | 1,416 22 always on | PJSC Rostelecom | |
| 92.124.128.0/18 since May 2019 | AS12389 | Residential | 1,497 738 always on | PJSC Rostelecom | |||
| 92.124.160.0/23 since Sep 2017 | AS12389 | Residential | 509 326 always on | PJSC Rostelecom | |||
| 92.124.160.0/24 since Mar 2018 | AS12389 | Residential | 255 169 always on | PJSC Rostelecom | |||
| 92.124.161.0/24 since Mar 2018 | AS12389 | Residential | 254 157 always on | PJSC Rostelecom | |||
| 92.124.162.0/23 since Sep 2017 | AS12389 | Residential | 511 336 always on | PJSC Rostelecom | |||
| 92.124.162.0/24 since Mar 2018 | AS12389 | Residential | 255 173 always on | PJSC Rostelecom | |||
| 92.124.163.0/24 since Mar 2018 | AS12389 | Residential | 256 163 always on | PJSC Rostelecom | |||
| 92.124.192.0/19 since Mar 2015 | AS12389 | Residential | 1,396 93 always on | PJSC Rostelecom | |||
| 92.124.204.0/23 since Apr 2017 | AS12389 | Residential | 511 49 always on | PJSC Rostelecom | |||
| 92.124.204.0/24 since Dec 2017 | AS12389 | Residential | 255 28 always on | PJSC Rostelecom | |||
| 92.124.205.0/24 since Dec 2017 | AS12389 | Residential | 256 21 always on | PJSC Rostelecom | |||
| 92.124.206.0/23 since Apr 2017 | AS12389 | Residential | 512 39 always on | PJSC Rostelecom | |||
| 92.124.206.0/24 since Dec 2017 | AS12389 | Residential | 256 19 always on | PJSC Rostelecom | |||
| 92.124.207.0/24 since Dec 2017 | AS12389 | Residential | 256 20 always on | PJSC Rostelecom | |||
| 92.124.208.0/21 since Jan 2017 | AS12389 | Residential | 340 | PJSC Rostelecom | |||
| 92.124.224.0/21 since Jun 2025 | AS12389 | Residential | 8 1 always on | PJSC Rostelecom | |||
| 92.124.239.0/24 since Feb 2018 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.124.240.0/20 since Mar 2024 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.125.0.0/17 since Feb 2018 | AS12389 | Residential | 1,561 69 always on | PJSC Rostelecom | |||
| 92.125.0.0/19 since Feb 2018 | AS12389 | Residential | 702 12 always on | PJSC Rostelecom | |||
| 92.125.0.0/21 since Nov 2020 | AS12389 | Residential | 348 5 always on | PJSC Rostelecom | |||
| 92.125.8.0/22 since Aug 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.125.12.0/22 since Aug 2020 | AS12389 | Residential | 221 5 always on | PJSC Rostelecom | |||
| 92.125.16.0/21 since Nov 2020 | AS12389 | Residential | 130 1 always on | PJSC Rostelecom | |||
| 92.125.24.0/22 since Nov 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.125.28.0/23 since Nov 2020 | AS12389 | Residential | PJSC Rostelecom | ||||
| 92.125.40.0/21 since Feb 2020 | AS12389 | Residential | 269 14 always on | PJSC Rostelecom | |||
| 92.125.48.0/20 since Apr 2020 | AS12389 | Residential | 549 36 always on | PJSC Rostelecom | |||
| 92.125.128.0/17 since Aug 2016 | AS12389 | Residential | 1,097 8 always on | PJSC Rostelecom | |||
| 92.125.128.0/20 since Oct 2022 | AS12389 | Residential | 602 | PJSC Rostelecom | |||
| 92.125.144.0/21 since Nov 2021 | AS12389 | Residential | 472 2 always on | PJSC Rostelecom | |||
| 92.126.0.0/18 since Jul 2015 | AS12389 | Residential | 2,367 196 always on | PJSC Rostelecom | |||
| 92.126.0.0/19 since Dec 2024 | AS12389 | Residential | 1,192 90 always on | PJSC Rostelecom | |||
| 92.126.32.0/19 since Dec 2024 | AS12389 | Residential | 1,175 106 always on | PJSC Rostelecom | |||
| 92.126.64.0/18 since Mar 2016 | AS12389 | Residential | 2,235 249 always on | PJSC Rostelecom | |||
| 92.126.64.0/19 since Oct 2017 | AS12389 | Residential | 1,210 1 always on | PJSC Rostelecom | |||
| 92.126.96.0/19 since Oct 2017 | AS12389 | Residential | 30.04%VPN | VPN servicesoperated by VPN Gate | 1,025 248 always on | PJSC Rostelecom | |
| 92.126.128.0/19 since Mar 2015 | AS12389 | Residential | 664 3 always on | PJSC Rostelecom | |||
| 92.126.128.0/20 since Aug 2016 | AS12389 | Residential | 640 | PJSC Rostelecom | |||
| 92.126.192.0/19 since Dec 2015 | AS12389 | Residential | 170 9 always on | PJSC Rostelecom | |||
| 92.126.224.0/19 since Sep 2015 | AS12389 | Residential | 36 3 always on | PJSC Rostelecom | |||
| 92.126.240.0/20 since Mar 2025 | AS12389 | Residential | 29 3 always on | PJSC Rostelecom | |||
| 92.127.0.0/17 since Feb 2018 | AS12389 | Residential | 5,230 1 always on | PJSC Rostelecom | |||
| 92.127.128.0/17 since Aug 2016 | AS12389 | Residential | 3,718 10 always on | PJSC Rostelecom | |||
| 92.127.144.0/21 since Sep 2021 | AS12389 | Residential | 376 4 always on | PJSC Rostelecom | |||
| 92.127.160.0/19 since Oct 2021 | AS12389 | Residential | 1,895 6 always on | PJSC Rostelecom | |||
| 92.127.192.0/18 since Dec 2021 | AS12389 | Residential | 1,444 | 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 |
|---|---|---|---|---|---|---|
| 92.124.0.0/14 | 262,144 | RU-RTK-20071116 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | May 22, 2008 | abuse@ |
| └ 92.124.0.0/18 | 16,384 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 26, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.0.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92.124.8.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 14, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.12.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.16.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.64.0/18 | 16,384 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 26, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.64.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92.124.96.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92. | 768 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 14, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.115.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.116.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.120.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.128.0/18 | 16,384 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 26, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.128.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92.124.144.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.160.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.192.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 26, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.192.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92. | 1,536 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 14, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.206.0/23 | 512 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.208.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.224.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 18, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.232.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | May 20, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.124.236.0/23 | 512 | SIBIRTELECOM-SFARM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.238.0/24 | 256 | SIBIRTELECOM-LINKS | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 16, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.124.239.0/24 | 256 | SIBIRTELECOM-NCC | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.240.0/20 | 4,096 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 28, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.124.240.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.124.248.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.125.0.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 28, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.125.0.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92.125.8.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.125.16.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.125.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 28, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.125.64.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 16, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.125.128.0/17 | 32,768 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Nov 26, 2007 | abuse@ via RU-RTK-20071116 |
| └ 92.125.128.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Dec 14, 2007 | abuse@ via RU-SIBNET |
| └ 92. | 2,816 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 14, 2008 | abuse@ via RU-SIBNET |
| └ 92. | 5,376 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.125.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 6, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.0.0/18 | 16,384 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Jul 31, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.126.0.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Sep 1, 2008 | abuse@ via RU-SIBNET |
| └ 92. | 3,072 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Sep 1, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.16.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 17, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 17, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.64.0/18 | 16,384 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Jul 31, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.126.64.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Sep 5, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.80.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 17, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.96.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 17, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.112.0/21 | 2,048 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 2, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.120.0/21 | 2,048 | WEBSTREAM | OJSC "Rostelecom" | ASSIGNED PA | Oct 2, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.128.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 2, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.126.144.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 3, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.126.148.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 3, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.126.152.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Feb 1, 2011 | abuse@ via RU-RTK-20071116 |
| └ 92.126.156.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 14, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.126.160.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Aug 7, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92. | 7,168 | WEBSTREAM | OJSC "Sibirtelecom" of the OJSC Sibirtelecom | ASSIGNED PA | Dec 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.188.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" of the OJSC Sibirtelecom | ASSIGNED PA | Dec 23, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.192.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Jul 31, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.126.192.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.208.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 2, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.224.0/19 | 8,192 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Jul 31, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92.126.224.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via RU-SIBNET |
| └ 92.126.224.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.225.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.226.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.227.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.228.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.229.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.230.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.231.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.232.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.233.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.234.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.235.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.236.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.237.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.238.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92.126.239.0/24 | 256 | WEBSTREAM | unknown | SUB-ALLOCATED PA | Aug 26, 2025 | abuse@ via WEBSTREAM |
| └ 92. | 3,072 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 20, 2008 | abuse@ via RU-SIBNET |
| └ 92.126.252.0/22 | 1,024 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 20, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.0.0/17 | 32,768 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Mar 16, 2010 | abuse@ via RU-RTK-20071116 |
| └ 92.127.0.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.16.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Oct 2, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.32.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 17, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.64.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 22, 2010 | abuse@ via RU-SIBNET |
| └ 92.127.80.0/20 | 4,096 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Mar 22, 2010 | abuse@ via RU-SIBNET |
| └ 92.127.96.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Apr 21, 2010 | abuse@ via RU-SIBNET |
| └ 92.127.128.0/17 | 32,768 | RU-SIBNET | unknown | LIR-PARTITIONED PA | Jul 31, 2008 | abuse@ via RU-RTK-20071116 |
| └ 92. | 6,144 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Sep 5, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.152.0/24 | 256 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 29, 2009 | abuse@ via RU-SIBNET |
| └ 92.127.153.0/25 | 128 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Jan 28, 2009 | abuse@ via RU-SIBNET |
| └ 92.127.153.128/25 | 128 | SIBNET-IPTV | IPTV platform of OJSC "Sibirtelecom" | ASSIGNED PA | Jan 28, 2009 | abuse@ via RU-SIBNET |
| └ 92. | 1,280 | WEBSTREAM | OJSC "Rostelecom" | ASSIGNED PA | Jan 28, 2009 | abuse@ via RU-SIBNET |
| └ 92.127.159.0/24 | 256 | SIBNET-TELEMATIC | OJSC "Sibirtelecom" | ASSIGNED PA | Sep 5, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.160.0/19 | 8,192 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 13, 2008 | abuse@ via RU-SIBNET |
| └ 92.127.192.0/18 | 16,384 | WEBSTREAM | OJSC "Sibirtelecom" | ASSIGNED PA | Nov 13, 2008 | abuse@ 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
262,144 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 261,883 | >99% | 64 | |
| Business | 256 | 0.10% | 2 | |
| 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
- Mar 2009
- Current origin since
- Aug 2016 · 10 yr
- Origin networks
- 2
- Last change of origin
- Jun 2016
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 92.
124. 0. 0/ 14 - Netname
- RU-RTK-20071116
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- May 22, 2008
- Updated
- Jun 6, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Nov 16, 2007
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE