Data as of Nov 6, 2026
46.183.128.0/21
1 anonymizer address · 0.05% · VPN510 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Residential-proxy exits
Proxy exits
510
25% of its addresses · 30 days
Always-on exits
33
6.5% of its exits
Spread
8 of 8
/24s with at least one exit
Providers
95
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
102K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 46.183.131.0/24 | 12 | 243 | |
| 46.183.128.0/24 | 9 | 136 | |
| 46.183.135.0/24 | 5 | 21 | |
| 46.183.130.0/24 | 3 | 11 | |
| 46.183.134.0/24 | 2 | 16 | |
| 46.183.132.0/24 | 1 | 29 | |
| 46.183.133.0/24 | 1 | 28 | |
| 46.183.129.0/24 | 0 | 27 |
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
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- Kookey
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NextProxy
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PacketStream
- 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
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
IPv4 market
Path
2 · Leased from
not leased
Operators, sellers and brokers
VPN services
| Name | Parent | In 46.183.128.0/21 | /24s |
|---|---|---|---|
| VPN Gate | University of Tsukuba | 10.05% | 1 |
Lineage
How this block came to its use, oldest first. The whole IPv4 market →
46.183.128.0/21
From the registry to its use
- Dec 8, 2010Registry recordJSC "Redcom-lnternet"ALLOCATED PA46.183.128.0/21
- Dec 8, 2010Route objectAS8749 JSC 'Redcom-lnternet'RIPE route object for AS8749 JSC 'Redcom-lnternet', maintainer REDCOM-MNT
- Dec 15, 2010– Nov 22, 2012
- Oct 2, 2018Route objectAS8749 JSC 'Redcom-lnternet'RIPE route object for AS8749 JSC 'Redcom-lnternet', maintainer REDCOM-MNT46.183.128.0/22
- Oct 2, 2018Route objectAS8749 JSC 'Redcom-lnternet'RIPE route object for AS8749 JSC 'Redcom-lnternet', maintainer REDCOM-MNT46.183.132.0/23
- Oct 4, 2018Route objectAS8749 JSC 'Redcom-lnternet'RIPE route object for AS8749 JSC 'Redcom-lnternet', maintainer REDCOM-MNT46.183.134.0/23
- Sep 13, 2022– today
- todayUsedVPN GateVPN
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 |
|---|---|---|---|---|---|---|
| 46.183.128.0/21 | 2,048 | RU-REDCOM-20101208 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ALLOCATED PA | Dec 8, 2010 | abuse@ |
| └ 46.183.128.0/23 | 512 | REDCOM-BB-UNLIM-4 | REDCOM Broadband Block 4 for flat-rate access | ASSIGNED PA | Dec 14, 2016 | abuse@ via RU-REDCOM-20101208 |
| └ 46.183.130.0/23 | 512 | REDCOM-BB-FLAT-4 | REDCOM Broadband Block 4 for flat-rate access in Khabarovsk | ASSIGNED PA | Dec 14, 2016 | abuse@ via RU-REDCOM-20101208 |
| └ 46.183.132.0/23 | 512 | REDCOM-BB-FLAT-5 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ASSIGNED PA | Jul 29, 2014 | abuse@ |
| └ 46.183.134.0/24 | 256 | REDCOM-DEDICATED-134 | REDCOM Broadband Block for dedicated access in Khabarovsk | ASSIGNED PA | Sep 19, 2022 | abuse@ via RU-REDCOM-20101208 |
| └ 46.183.135.0/24 | 256 | REDCOM-BB-KHV-FLAT-30 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ASSIGNED PA | Jul 29, 2014 | abuse@ |
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
2,048 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 2,047 | >99% | 2 | |
| VPNanonymizer | 1 | 0.05% | 1 |
Network & registry
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Dec 2010
- Current origin since
- Sep 2022 · 4.1 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 46.183.128.0/21 | AS8749 | /21 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8749 | RIPE | REDCOM LIR BLOCK 3 | REDCOM-MNT | Dec 8, 2010 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 46.183.128.0/22 | AS8749 | RIPE | REDCOM LIR BLOCK 3 Sub | REDCOM-MNT | Oct 2, 2018 |
| 46.183.132.0/23 | AS8749 | RIPE | REDCOM LIR BLOCK 3 Sub | REDCOM-MNT | Oct 4, 2018 |
| 46.183.134.0/23 | AS8749 | RIPE | REDCOM LIR BLOCK 3 Subroute | REDCOM-MNT | Sep 19, 2022 |
Whois
Registration for this announcement
- Range
- 46.
183. 128. 0/ 21 - Netname
- RU-REDCOM-20101208
- Registrant
- JSC "Redcom-lnternet"
- Registrant country
- RU
- Organization
- JSC "Redcom-lnternet" (ORG-RA23-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Dec 8, 2010
- Updated
- Mar 6, 2025
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Dec 8, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
redcom. ru - Name
- REDCOM ABUSE
- Handle
- RA6664-RIPE