Data as of Nov 8, 2026
37.110.128.0/19
263 residential-proxy exits · 30 daysPJSC Rostelecom
Residential-proxy exits
Proxy exits
263
3.2% of its addresses · 30 days
Always-on exits
21
8.0% of its exits
Spread
28 of 32
/24s with at least one exit
Providers
100
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
41K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 37.110.130.0/24 | 3 | 16 | |
| 37.110.147.0/24 | 3 | 15 | |
| 37.110.159.0/24 | 3 | 11 | |
| 37.110.133.0/24 | 1 | 18 | |
| 37.110.149.0/24 | 1 | 15 | |
| 37.110.152.0/24 | 1 | 14 | |
| 37.110.135.0/24 | 1 | 14 | |
| 37.110.128.0/24 | 1 | 13 | |
| 37.110.151.0/24 | 1 | 12 | |
| 37.110.145.0/24 | 1 | 9 | |
| 37.110.153.0/24 | 1 | 8 | |
| 37.110.157.0/24 | 1 | 8 | |
| 37.110.158.0/24 | 1 | 6 | |
| 37.110.141.0/24 | 1 | 4 | |
| 37.110.131.0/24 | 1 | 3 | |
| 37.110.144.0/24 | 0 | 13 | |
| 37.110.129.0/24 | 0 | 12 | |
| 37.110.148.0/24 | 0 | 11 | |
| 37.110.155.0/24 | 0 | 10 | |
| 37.110.132.0/24 | 0 | 8 | |
| 37.110.150.0/24 | 0 | 8 | |
| 37.110.134.0/24 | 0 | 7 | |
| 37.110.154.0/24 | 0 | 7 | |
| 37.110.143.0/24 | 0 | 6 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LUMIPROXY
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- MoMoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
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 |
|---|---|---|---|---|---|---|
| 37. | 40,960 | RU-RTK-20120208 | PJSC Rostelecom (ORG-JR8-RIPE) · RU | ALLOCATED PA | Feb 9, 2012 | abuse@ |
| └ 37.110.128.0/20 | 4,096 | NCN-BBCUST | NCNET Broadband customers | ASSIGNED PA | Jul 27, 2026 | abuse@ via RU-RTK-20120208 |
| └ 37.110.144.0/20 | 4,096 | NCN-BBCUST | NCNET Broadband customers | ASSIGNED PA | Jul 27, 2026 | abuse@ via RU-RTK-20120208 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Origin network
AS42610
RU
- Name
- PJSC Rostelecom
- Type
- Internet provider
- Registered
- Mar 22, 2007
- Domain
- rt.ru
- Website
- moscow.rt.ru
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2012
- Current origin since
- Feb 2012 · 15 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 37.
110. 0. 0 - 37. 110. 159. 255 - Netname
- RU-RTK-20120208
- Registrant
- PJSC Rostelecom
- Registrant country
- RU
- Organization
- PJSC Rostelecom (ORG-JR8-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Feb 9, 2012
- Updated
- Jun 22, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 8, 2012
- Status
- assigned
Report abuse
Abuse contact
- abuse@
rt. ru - Name
- PJSC Rostelecom Technical Team
- Handle
- RTNC-RIPE