Data as of Nov 6, 2026
92.37.128.0/17
9 anonymizer addresses · 0.03% · VPN8,371 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
8,371
26% of its addresses · 30 days
Always-on exits
527
6.3% of its exits
Spread
128 of 128
/24s with at least one exit
Providers
107
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
1.2M observations
- VPN · anonymizer
- Residential
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 92.37.143.0/24 | 221 | 256 | |
| 92.37.142.0/24 | 219 | 255 | |
| 92.37.198.0/24 | 4 | 67 | |
| 92.37.170.0/24 | 4 | 66 | |
| 92.37.221.0/24 | 3 | 62 | |
| 92.37.187.0/24 | 3 | 58 | |
| 92.37.168.0/24 | 2 | 75 | |
| 92.37.233.0/24 | 2 | 73 | |
| 92.37.149.0/24 | 2 | 68 | |
| 92.37.215.0/24 | 2 | 68 | |
| 92.37.151.0/24 | 2 | 68 | |
| 92.37.247.0/24 | 2 | 67 | |
| 92.37.230.0/24 | 2 | 66 | |
| 92.37.139.0/24 | 2 | 66 | |
| 92.37.133.0/24 | 2 | 66 | |
| 92.37.140.0/24 | 2 | 65 | |
| 92.37.176.0/24 | 2 | 64 | |
| 92.37.217.0/24 | 2 | 59 | |
| 92.37.252.0/24 | 2 | 57 | |
| 92.37.153.0/24 | 2 | 55 | |
| 92.37.201.0/24 | 2 | 51 | |
| 92.37.204.0/24 | 1 | 80 | |
| 92.37.191.0/24 | 1 | 76 | |
| 92.37.128.0/24 | 1 | 74 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- 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
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 92.37.128.0/17 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 90.03% | 8 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
92.37.128.0/17
From the registry to its use
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.37.128.0/18 since Feb 2008 | AS34584 | Residential | 4,401 483 always on | PJSC Rostelecom | |||
| 92.37.128.0/21 since Feb 2016 | AS12389 | Residential | 495 7 always on | PJSC Rostelecom | |||
| 92.37.136.0/22 since Feb 2015 | AS12389 | Residential | 253 2 always on | PJSC Rostelecom | |||
| 92.37.140.0/23 since Mar 2015 | AS12389 | Residential | 129 2 always on | PJSC Rostelecom | |||
| 92.37.142.0/23 since Oct 2014 | AS12389 | Residential | 30.59%VPN | VPN servicesoperated by VPN Gate | 511 440 always on | PJSC Rostelecom | |
| 92.37.144.0/21 since Dec 2017 | AS12389 | Residential | 528 5 always on | PJSC Rostelecom | |||
| 92.37.152.0/21 since Dec 2017 | AS12389 | Residential | 488 3 always on | PJSC Rostelecom | |||
| 92.37.160.0/21 since Dec 2017 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 490 4 always on | PJSC Rostelecom | |
| 92.37.168.0/21 since Dec 2017 | AS12389 | Residential | 525 9 always on | PJSC Rostelecom | |||
| 92.37.176.0/21 since Jun 2016 | AS12389 | Residential | 461 7 always on | PJSC Rostelecom | |||
| 92.37.184.0/21 since Dec 2017 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 521 4 always on | PJSC Rostelecom | |
| 92.37.192.0/18 since Feb 2008 | AS34584 | Residential | 3,970 44 always on | PJSC Rostelecom | |||
| 92.37.192.0/21 since Dec 2017 | AS12389 | Residential | 20.10%VPN | VPN servicesoperated by VPN Gate | 465 7 always on | PJSC Rostelecom | |
| 92.37.200.0/21 since Dec 2017 | AS12389 | Residential | 517 5 always on | PJSC Rostelecom | |||
| 92.37.208.0/21 since Dec 2017 | AS12389 | Residential | 520 5 always on | PJSC Rostelecom | |||
| 92.37.216.0/21 since Dec 2017 | AS12389 | Residential | 505 7 always on | PJSC Rostelecom | |||
| 92.37.224.0/21 since Jun 2016 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 477 4 always on | PJSC Rostelecom | |
| 92.37.232.0/21 since Dec 2017 | AS12389 | Residential | 10.05%VPN | VPN servicesoperated by VPN Gate | 513 6 always on | PJSC Rostelecom | |
| 92.37.240.0/21 since Jul 2015 | AS12389 | Residential | 494 3 always on | PJSC Rostelecom | |||
| 92.37.248.0/21 since Dec 2017 | AS12389 | Residential | 479 7 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 |
|---|---|---|---|---|---|---|
| 92.37.128.0/17 | 32,768 | RU-RTK-20080118 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Jan 18, 2008 | abuse@ |
| └ 92.37.128.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-210 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.129.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-234 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.130.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-234 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.132.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-499 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.133.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-30 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.134.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-30 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.136.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-30 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.140.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-30 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.142.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-51 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.144.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-436 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.146.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-300 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.148.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-4946 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.148.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-297 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.149.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-297 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.150.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-425 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.152.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-425 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.154.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-21 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.156.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-21 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.160.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-484 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.162.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-484 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.163.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-36 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.164.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-36 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.166.0/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, HONET-17 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.166.64/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, HONET-6 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.166.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, DLC-4 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.167.0/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, DLC-1 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.167.64/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, DLC-2 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.167.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, DLC-3 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.167.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, DLC-5 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.168.0/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, HONET-14 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.168.64/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, HONET-16 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.168.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-2934 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.168.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-493 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.169.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-430 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.170.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-430 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.172.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-533 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.173.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-533 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.173.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-536 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.174.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-536 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.175.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-291 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.175.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-293 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.176.0/21 | 2,048 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-51 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.184.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-34 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.188.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-715 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.190.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-715 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.190.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-718 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.191.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Khabarovsk city, ATS-718 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.192.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-220 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.196.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-220 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.197.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-220 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.198.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-271 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.198.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-272 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.199.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-273 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.199.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-274 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.200.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-591 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.202.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-591 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.203.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-591 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.203.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-578 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.204.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-578 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.206.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-578 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.207.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-5610 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.207.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-563 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.207.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-564 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.208.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.212.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.214.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-530 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.216.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-530 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.218.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-540 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.220.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Komsomolsk-at-Amur town, ATS-37 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.221.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Amursk town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.222.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Amursk town, ATS-310 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.222.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Amursk town, ATS-280 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.223.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Troitskoe village, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.223.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Troitskoe village, ATS-474 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.224.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town ATS-465 | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.224.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town ATS-468 | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.225.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town ATS-66 | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.225.128/25 | 128 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town ATS-97 | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.226.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town central | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.228.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Sovetskaya Gavan, town ATS-63 | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.229.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Vanino village, ATS-75 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.230.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Vanino village, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.232.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.236.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-48 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.236.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-48 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.236.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-792 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.237.0/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-711 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.237.64/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-741 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.237.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-752 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.237.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-782 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.238.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.239.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-46 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.240.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.242.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-3 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.244.0/22 | 1,024 | KHT-XDSL | PPPoE xDSL links in Birobidjan town, ATS-3 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.248.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Leninskoe village, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.250.0/26 | 64 | KHT-XDSL | PPPoE xDSL links in Leninskoe village, ATS-2470 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.250.64/26 | 64 | KHT-XDSL | PPPoE xDSL links in Leninskoe village, ATS-3900 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.250.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Leninskoe village, ATS-4020 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.250.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Leninskoe village, ATS-4720 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.251.0/25 | 128 | KHT-XDSL | PPPoE xDSL links in Obluchie village, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.251.128/26 | 64 | KHT-XDSL | PPPoE xDSL links in Obluchie village, ATS-44 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.251.192/26 | 64 | KHT-XDSL | PPPoE xDSL links in Obluchie village, ATS-320 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.252.0/23 | 512 | KHT-XDSL | PPPoE xDSL links in Nikolaevsk-at-Amur town, ATS-220 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.254.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Nikolaevsk-at-Amur town, central node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
| └ 92.37.255.0/24 | 256 | KHT-XDSL | PPPoE xDSL links in Nikolaevsk-at-Amur town, ATS-27 node | ASSIGNED PA | Nov 18, 2008 | abuse@ via RU-RTK-20080118 |
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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 32,759 | >99% | 27 | |
| VPNanonymizer | 9 | 0.03% | 9 |
Network & registry
Origin network
AS34584
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Feb 17, 2005
- Domain
- kht.ru
- Industry
- Computer and Information Technology
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2008
- Current origin since
- Feb 2008 · 19 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 92.
37. 128. 0/ 17 - Netname
- RU-RTK-20080118
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Jan 18, 2008
- Updated
- Jun 23, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Jan 18, 2008
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE