Data as of Nov 6, 2026
92.37.128.0/18
5 anonymizer addresses · 0.03% · VPN4,397 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
4,397
27% of its addresses · 30 days
Always-on exits
483
11% of its exits
Spread
64 of 64
/24s with at least one exit
Providers
106
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
947K 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.170.0/24 | 4 | 66 | |
| 92.37.187.0/24 | 3 | 58 | |
| 92.37.168.0/24 | 2 | 75 | |
| 92.37.151.0/24 | 2 | 68 | |
| 92.37.149.0/24 | 2 | 68 | |
| 92.37.133.0/24 | 2 | 66 | |
| 92.37.139.0/24 | 2 | 66 | |
| 92.37.140.0/24 | 2 | 65 | |
| 92.37.176.0/24 | 2 | 64 | |
| 92.37.153.0/24 | 2 | 55 | |
| 92.37.191.0/24 | 1 | 76 | |
| 92.37.128.0/24 | 1 | 74 | |
| 92.37.173.0/24 | 1 | 71 | |
| 92.37.166.0/24 | 1 | 67 | |
| 92.37.131.0/24 | 1 | 65 | |
| 92.37.165.0/24 | 1 | 64 | |
| 92.37.159.0/24 | 1 | 63 | |
| 92.37.144.0/24 | 1 | 62 | |
| 92.37.175.0/24 | 1 | 61 | |
| 92.37.182.0/24 | 1 | 60 | |
| 92.37.181.0/24 | 1 | 59 | |
| 92.37.132.0/24 | 1 | 59 |
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
- 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/18 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 50.03% | 4 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
92.37.128.0/18
From the registry to its use
- Jan 18, 2008Registry recordPJSC RostelecomALLOCATED PA92.37.128.0/17
- Feb 1, 2008– today
- Feb 1, 2008– today
- Nov 6, 2018Route objectAS34584 PJSC RostelecomRIPE route object for AS34584 PJSC Rostelecom, maintainer ROSTELECOM-MNT
- todayUsedVPN GateVPN
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 92.37.128.0/17 since Feb 2008 | AS34584 | Residential | 8,371 527 always on | PJSC Rostelecom |
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/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 |
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 |
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
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 16,379 | >99% | 15 | |
| VPNanonymizer | 5 | 0.03% | 5 |
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
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2008
- Current origin since
- Feb 2008 · 19 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 92.37.128.0/18 | AS34584 | /18 | RIPE | RPKI valid |
| 92.37.128.0/17 | AS34584 | /17 | RIPE | Too specific |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS34584 | RIPE | ROSTELECOM-MNT | Oct 23, 2025 |
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