Data as of Nov 20, 2026
212.19.23.0/24
22 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Announced by
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby
Residential-proxy exits
Proxy exits
22
8.6% of its addresses · 30 days
Always-on exits
3
14% of its exits
Providers
64
selling exits here
Oct 21, 2026 – Nov 19, 2026
Exits seen per day
12K observations
Proxy providers listing exits
- 2Captcha
- 711Proxy
- AETHYN_ELITE
- ASHBURNPROXIES
- Ake.net
- B2Proxy
- BirdProxies
- BottingTools
- BuyingProxy
- ByteProxies
- Byteful
- CYBERYOZH
- CliProxy
- Datarama
- EZProxies
- EnigmaProxy
- Evomi
- FLAMEPROXIES_BASIC
- FLAMEPROXIES_PREMIUM
- FLEETPROXY
- FlashProxy
- FlexyProxies
- FloppyData
- GEEKPROXY_FLEX
- GEEKPROXY_TURBO
- GSocks
- Geonode
- GonzoProxy
- HASDATA
- IPFly
- IPOasis
- IPPeak
- IPROCKET_BASIC
- Infatica
- InfiniteProxies
- LITPORT_LIMA
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NSocks
- NodeMaven
- NodeProxy
- NovaProxy
- PROXYLANE
- PROXYSCRAPE
- Proxiware
- Proxy-Seller
- ProxyEmpire
- ProxyGeo
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- ResiProxies
- RolaProxy
- SOTAPROXY
- Shifter
- Smartproxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.19.0.0/19 since May 2005 | AS8749 | Residential | 441 57 always on | JSC "Redcom-lnternet" |
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 |
|---|---|---|---|---|---|---|
| 212.19.0.0/19 | 8,192 | RU-REDCOM-980323 | JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RU | ALLOCATED PA | — | abuse@ |
| └ 212.19.20.0/22 | 1,024 | REDCOM-BB-2 | REDCOM Broadband Block 2 | ASSIGNED PA | Aug 12, 2008 | 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
Announced by
Covering announcement 212.19.20.0/22
- Prefix
- 212.19.20.0/22
- Announced by
- AS8749 JSC 'Redcom-lnternet'
- Type
- Residential
- Proxy exits
- 102
- Always-on exits
- 21
- RPKI
- RPKI valid
- Netname
- REDCOM-BB-2
- Registrant
- REDCOM Broadband Block 2
- RIR
- RIPE NCC
IPv4 market
Holder
- Organization
- JSC "Redcom-lnternet"
- Handle
- ORG-RA23-RIPE
- Range
- 212.
19. 0. 0/ 19 - Registration type
- ALLOCATED PA
Routing timeline
Covering aggregate above, the prefix's own history below
212.19.20.0/22
Routing history
- Pattern
- Stable
- First seen
- Sep 2008
- Current origin since
- Jul 2025 · 1.3 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 212.19.20.0/22 | AS8749 | /22 | RIPE | RPKI valid |
| 212.19.0.0/19 | AS8749 | /19 | RIPE | Too specific |
IRR
Route objects on 212.19.20.0/22
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS8749 | RIPE | REDCOM-BB-2 | REDCOM-MNT | Sep 3, 2008 |
Whois
Registration for this announcement
- Range
- 212.
19. 20. 0/ 22 - Netname
- REDCOM-BB-2
- Registrant
- REDCOM Broadband Block 2
- Registrant country
- RU
- Organization
- REDCOM Broadband Block 2
- Org country
- RU
- Type
- ASSIGNED PA
- Created
- Aug 12, 2008
- Updated
- Mar 6, 2025
- Maintainer
- REDCOM-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