Data as of Nov 8, 2026
212.19.16.0/23
22 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Residential-proxy exits
Proxy exits
22
4.3% of its addresses · 30 days
Always-on exits
2
9.1% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
3.2K observations
Proxy providers listing exits
- Ake.net
- BartProxies
- BirdProxies
- ByteProxies
- Byteful
- CliProxy
- EnigmaProxy
- GSocks
- Geonix
- IPFly
- Infatica
- LemonLabs
- LemonPrime
- MangoProxy
- NodeProxy
- NovProxy
- NovaProxy
- PROXYWING_BASIC
- Proxiware
- Proxy-Seller
- ProxyEmpire
- Proxyma
- PuraRoute
- RainProxy
- SPYDERPROXY_PREMIUM
- Shifter
- VantageProxies
- VitalExclusive
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.19.0.0/19 since May 2005 | AS8749 | Residential | 448 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.16.0/24 | 256 | REDCOM-BB-7 | REDCOM Broadband Block 7 | ASSIGNED PA | Sep 8, 2011 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.0/30 | 4 | REDCOM-CLNT-DKA | DKA COMPANY Ltd | ASSIGNED PA | Jul 27, 2014 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.8/29 | 8 | REDCOM-CLNT-FlyAurora | JSC "Aurora Airlines" | ASSIGNED PA | Apr 25, 2014 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.20/30 | 4 | REDCOM-CLNT-Polinom | "Polinom" Co, ltd | ASSIGNED PA | Mar 15, 2012 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.24/29 | 8 | DELTALIZING-CLNT-REDCOM | ZAO "DeltaLizing" | ASSIGNED PA | Sep 20, 2006 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.32/29 | 8 | PRESENTDV-CLNT-REDCOM | Kompania Present Ltd. | ASSIGNED PA | Aug 17, 2016 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.48/29 | 8 | REDCOM-CLNT-UstSrednekanGESStroi-Len57 | unknown | ASSIGNED PA | Oct 14, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.56/29 | 8 | REDCOM-CLNT-IVI | unknown | ASSIGNED PA | Nov 18, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.64/29 | 8 | REDCOM-CLNT-RusMyasoMolTorg | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.72/29 | 8 | REDCOM-CLNT-ESCORUS | unknown | ASSIGNED PA | Feb 2, 2022 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.80/29 | 8 | REDCOM-CLNT-SSMP | unknown | ASSIGNED PA | Dec 29, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.88/29 | 8 | REDCOM-CLNT-EMERCOM_ | unknown | ASSIGNED PA | Dec 30, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.96/27 | 32 | REDCOM-CLNT-N-Kraft | unknown | ASSIGNED PA | Dec 6, 2019 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.128/27 | 32 | INTOURKHAB-CLNT-REDCOM | Intour-Khabarovsk network | ASSIGNED PA | — | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.160/29 | 8 | REDCOM-CLNT-Spektr | unknown | ASSIGNED PA | Feb 11, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.168/29 | 8 | REDCOM-CLNT-CVT | CVT Co., ltd | ASSIGNED PA | Jun 3, 2013 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.176/28 | 16 | REDCOM-CLNT-EMP | State Unitary Enterprise Emporium | ASSIGNED PA | Mar 27, 2002 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.192/28 | 16 | REDCOM-CLNT-Viveya | unknown | ASSIGNED PA | Dec 13, 2019 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.208/29 | 8 | REDCOM-CLNT-UdinskGold | unknown | ASSIGNED PA | Mar 17, 2021 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.216/29 | 8 | FE-AIRBASE-CLNT-REDCOM | Far East Air Base for forest fire fighting | ASSIGNED PA | Sep 5, 2003 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.17.224/27 | 32 | REDCOM-CLNT-IPKSZ | Postgraduate Institute of Public Health Care Specialists | ASSIGNED PA | Dec 4, 2018 | 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.16.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