Data as of Nov 5, 2026
185.3.182.0/23
1 anonymizer address · 0.20% · VPN499 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Residential-proxy exits
Proxy exits
499
97% of its addresses · 30 days
Always-on exits
10
2.0% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
93
selling exits here
Oct 6, 2026 – Nov 4, 2026
Exits seen per day
99K observations
- VPN · anonymizer
- Residential
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 185.3.183.0/24 | 7 | 245 | |
| 185.3.182.0/24 | 3 | 251 |
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
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- MangoProxy
- Maskify
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- TrustProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 185.3.182.0/23 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 10.20% | 1 |
Registrations in this block
The registry's network records over this block, widest first, each under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 185.3.180.0/22 | 1,024 | RU-REDCOM-20120321 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ALLOCATED PA | Sep 21, 2012 | abuse@ |
| └ 185.3.182.0/23 | 512 | REDCOM-BB-KHV-FLAT-2 | REDCOM Broadband Block 2 for flat-rate access in Khabarovsk | ASSIGNED PA | Nov 9, 2012 | abuse@ via RU-REDCOM-20120321 |
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
512 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 511 | >99% | 2 | |
| VPNanonymizer | 1 | 0.20% | 1 |
Network & registry
Announced by
Covering announcement 185.3.180.0/22
- Prefix
- 185.3.180.0/22
- Announced by
- AS8749 JSC 'Redcom-lnternet'
- Type
- Residential
- Anonymizer addresses
- 2 addresses · 0.20%VPN
- Operator
- VPN servicesoperated by VPN Gate
- Proxy exits
- 1,001
- Always-on exits
- 26
- RPKI
- RPKI valid
- Netname
- RU-REDCOM-20120321
- Registrant
- JSC "Redcom-lnternet"
- RIR
- RIPE NCC
Routing timeline
Who has announced 185.3.180.0/22
185.3.180.0/22
Routing history
- Pattern
- Stable
- First seen
- Sep 2012
- Current origin since
- Sep 2012 · 14 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 185.3.180.0/22 | AS8749 | /22 | RIPE | RPKI valid |
IRR
Route objects on 185.3.180.0/22
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8749 | RIPE | REDCOM LIR BLOCK 6 Vladivostok | REDCOM-MNT | Jan 29, 2013 |
Whois
Registration for this announcement
- Range
- 185.
3. 180. 0/ 22 - Netname
- RU-REDCOM-20120321
- Registrant
- JSC "Redcom-lnternet"
- Registrant country
- RU
- Organization
- JSC "Redcom-lnternet" (ORG-RA23-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Sep 21, 2012
- Updated
- Mar 6, 2025
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Sep 21, 2012
- Status
- assigned
Report abuse
Abuse contact
- abuse@
redcom. ru - Name
- REDCOM ABUSE
- Handle
- RA6664-RIPE