Data as of Nov 6, 2026
212.19.26.0/23
6 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Residential-proxy exits
Proxy exits
6
1.2% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
35
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
1.3K observations
Proxy providers listing exits
- 2Captcha
- 711Proxy
- Ake.net
- BartProxies
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- EZProxies
- EnigmaProxy
- GSocks
- GonzoProxy
- HydraProxy
- IPFly
- IPPeak
- Infatica
- LightningProxies
- MangoProxy
- NodeProxy
- NovaProxy
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyHat
- Proxyma
- PuraRoute
- RainProxy
- RoamProxy
- Shifter
- Smartproxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.19.0.0/19 since May 2005 | AS8749 | Residential | 450 62 always on | JSC "Redcom-lnternet" |
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 |
|---|---|---|---|---|---|---|
| 212.19.0.0/19 | 8,192 | RU-REDCOM-980323 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ALLOCATED PA | — | abuse@ |
| └ 212.19.26.0/24 | 256 | REDCOM-DEDICATED-26 | Dedicated P2P customer connections | ASSIGNED PA | Aug 7, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.0/29 | 8 | REDCOM-CLNT-FOMS | unknown | ASSIGNED PA | Dec 28, 2018 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.8/29 | 8 | REDCOM-CLNT-AbonPOS | Redcom-Internet POS Units | ASSIGNED PA | Mar 15, 2012 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.16/29 | 8 | REDCOM-CLNT-Navigator | Navigator LLC | ASSIGNED PA | Jun 5, 2013 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.24/29 | 8 | REDCOM-CLNT-SatelecomDV-1 | unknown | ASSIGNED PA | Mar 12, 2018 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.32/30 | 4 | REDCOM-CLNT-Benda | BENDA LA COMPANY Ltd. | ASSIGNED PA | Apr 15, 2014 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.36/30 | 4 | KONTYR-CLNT-REDCOM | Trading Network "Kontyr" | ASSIGNED PA | Apr 23, 2003 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.40/29 | 8 | KONTYR-CLNT-REDCOM | Trading Network "Kontyr" | ASSIGNED PA | Jun 28, 2005 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.48/29 | 8 | REDCOM-CLNT-SV | unknown | ASSIGNED PA | Feb 25, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.56/29 | 8 | REDCOM-CLNT-CLINIC2 | State Agency of Medicine "Khabarovsk Clinic Regional Hospital # 2" | ASSIGNED PA | Jul 23, 2009 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.64/28 | 16 | REDCOM-CLNT-DirDorStroy | Federal state institution "Interregional management on road construction in the Far East region of Russia of Federal road agency" | ASSIGNED PA | Mar 15, 2012 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.80/28 | 16 | REDCOM-CLNT-KhabarovskADM1 | unknown | ASSIGNED PA | Jan 9, 2017 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.96/29 | 8 | REDCOM-CLNT-MetallExport | unknown | ASSIGNED PA | Feb 14, 2019 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.104/29 | 8 | REDCOM-CLNT-AmurShip | AmurShip Co, ltd | ASSIGNED PA | Mar 15, 2012 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.128/27 | 32 | MES-CLNT-REDCOM | Department of FGC UES - MGC of East | ASSIGNED PA | Oct 24, 2003 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.160/28 | 16 | REDCOM-CLNT-FESMU | unknown | ASSIGNED PA | Mar 19, 2020 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.176/29 | 8 | REDCOM-CLNT-Tenzor | unknown | ASSIGNED PA | Sep 6, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.192/29 | 8 | KHBSMENA-CLNT-REDCOM | Smena Traiding Co. LTD | ASSIGNED PA | Mar 26, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.200/29 | 8 | KONTYR-CLNT-REDCOM | Trading Network "Kontyr" | ASSIGNED PA | Jun 28, 2005 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.216/30 | 4 | REDCOM-CLNT-ContrSchetPalata | Control and Account Chamber of the Khabarovsk Territory | ASSIGNED PA | Dec 26, 2014 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.220/30 | 4 | REDCOM-CLNT-BusinessSviazHolding | unknown | ASSIGNED PA | Dec 10, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.224/29 | 8 | REDCOM-CLNT-OKHRANA | Federal state unitary enterprise "Ohrana" | ASSIGNED PA | Jul 4, 2007 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.232/29 | 8 | REDCOM-CLNT-LorCenter | unknown | ASSIGNED PA | Jul 31, 2020 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.27.240/28 | 16 | REDCOM-VATS | unknown | ASSIGNED PA | Dec 2, 2019 | abuse@ via RU-REDCOM-980323 |
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
Routing timeline
Covering aggregate above, the prefix's own history below
Summary
Routing history
- Pattern
- Stable
- First seen
- Jul 2025
- Current origin since
- Jul 2025 · 1.3 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.19.26.0/23 | AS8749 | /23 | RIPE | RPKI valid |
| 212.19.0.0/19 | AS8749 | /19 | RIPE | Too specific |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8749 | RIPE | REDCOM-MNT | Nov 5, 2025 |
Whois
Registration for this announcement
- Range
- 212.
19. 0. 0/ 19 - Netname
- RU-REDCOM-980323
- Registrant
- JSC "Redcom-lnternet"
- Registrant country
- RU
- Organization
- JSC "Redcom-lnternet" (ORG-RA23-RIPE)
- Org country
- RU
- Type
- ALLOCATED PA
- Created
- Not stated by the registry
- Updated
- Oct 28, 2026
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Mar 23, 1998
- Status
- assigned
Report abuse
Abuse contact
- abuse@
redcom. ru - Name
- REDCOM ABUSE
- Handle
- RA6664-RIPE