Data as of Nov 7, 2026
91.143.128.0/20
197 residential-proxy exits · 30 daysRegionset Ltd
Residential-proxy exits
Proxy exits
197
4.8% of its addresses · 30 days
Always-on exits
23
12% of its exits
Spread
10 of 16
/24s with at least one exit
Providers
101
selling exits here
Oct 8, 2026 – Nov 6, 2026
Exits seen per day
29K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 91.143.137.0/24 | 5 | 30 | |
| 91.143.135.0/24 | 5 | 27 | |
| 91.143.143.0/24 | 4 | 20 | |
| 91.143.134.0/24 | 3 | 25 | |
| 91.143.133.0/24 | 2 | 27 | |
| 91.143.132.0/24 | 2 | 21 | |
| 91.143.138.0/24 | 1 | 23 | |
| 91.143.142.0/24 | 1 | 17 | |
| 91.143.129.0/24 | 0 | 5 | |
| 91.143.139.0/24 | 0 | 2 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BlurPath
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- 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-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
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 |
|---|---|---|---|---|---|---|
| 91.143.128.0/20 | 4,096 | RU-REGIONSET-20061031 | Regionset Ltd (ORG-RL33-RIPE) · RU | ALLOCATED PA | Oct 31, 2006 | ncc@ |
| └ 91.143.128.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.129.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.130.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.131.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.132.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.133.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Nov 5, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.134.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Dec 14, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.135.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Feb 9, 2007 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.136.0/28 | 16 | GOTEK-NET | GOTEK Enterprises Group, Zheleznogorsk | ASSIGNED PA | Nov 3, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.136.16/28 | 16 | MGOK-NET | OJSC "Mikhailovsky GOK", Zheleznogorsk | ASSIGNED PA | Nov 3, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.137.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Mar 31, 2008 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.138.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Dec 14, 2006 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.139.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Apr 11, 2008 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.140.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Apr 17, 2008 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.141.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Apr 17, 2008 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.142.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Jan 21, 2013 | ncc@ via RU-REGIONSET-20061031 |
| └ 91.143.143.0/24 | 256 | REGIONSET | Regionset, Zheleznogorsk | ASSIGNED PA | Jan 21, 2013 | ncc@ via RU-REGIONSET-20061031 |
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
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 4,064 | >99% | 2 | |
| Business | 32 | 0.78% | 2 |
Network & registry
Origin network
AS41829
RU
- Name
- Regionset Ltd
- Type
- Internet provider
- Registered
- Oct 31, 2006
- Domain
- regionset.ru
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Nov 2006
- Current origin since
- Nov 2006 · 20 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS41829 | RIPE | REGIONSET | REGIONSET-MNT | Nov 2, 2006 |
Whois
Registration for this announcement
- Range
- 91.
143. 128. 0/ 20 - Netname
- RU-REGIONSET-20061031
- Registrant
- Regionset Ltd
- Registrant country
- RU
- Organization
- Regionset Ltd (ORG-RL33-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Oct 31, 2006
- Updated
- May 19, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Oct 31, 2006
- Status
- assigned
Report abuse
Abuse contact
- ncc@
rset. ru - Name
- Regionset Contact Role
- Handle
- RCR13-RIPE