Data as of Nov 12, 2026
212.19.4.0/22
73 residential-proxy exits · 30 daysJSC 'Redcom-lnternet'
Residential-proxy exits
Proxy exits
73
7.1% of its addresses · 30 days
Always-on exits
12
16% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
72
selling exits here
Oct 13, 2026 – Nov 11, 2026
Exits seen per day
41K observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 212.19.7.0/24 | 5 | 24 | |
| 212.19.6.0/24 | 3 | 20 | |
| 212.19.4.0/24 | 2 | 19 | |
| 212.19.5.0/24 | 2 | 10 |
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 911Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BestProxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Decodo
- EnigmaProxy
- Evomi
- FLEETPROXY
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- Geonode
- GonzoProxy
- HydraProxy
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- LUMIPROXY
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- MangoProxy
- NSocks
- NiuProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Oxylabs
- PROXYSCRAPE
- PrivateProxy
- Proxies.fo
- Proxiware
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- ResiProxies
- Shifter
- Smartproxy
- Thordata
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- ZENPROXY_PREMIUM
Announcements
Less specific
Covering announcements
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 212.19.0.0/19 since May 2005 | AS8749 | Residential | 441 53 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.4.0/24 | 256 | REDCOM-DEDICATED-4-1 | Dedicated P2P customer connections with unnumbered, block 2 | ASSIGNED PA | Jul 19, 2017 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.5.0/25 | 128 | REDCOM-DEDICATED-5 | Dedicated P2P customer connections | ASSIGNED PA | Dec 23, 2008 | abuse@ via RU-REDCOM-980323 |
| └ 212.19.5.128/25 | 128 | REDCOM-DEDICATED-5-2 | Dedicated P2P customer connections with unnumbered | ASSIGNED PA | Jun 23, 2013 | 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
- Oct 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.4.0/22 | AS8749 | /22 | 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