Data as of Nov 14, 2026

212.19.26.0/24

6 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
34
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • 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

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential439
54 always on
JSC "Redcom-lnternet"

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.19.0.0/198,192RU-REDCOM-980323JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RUALLOCATED PA—abuse@redcom.ru
└ 212.19.26.0/24256REDCOM-DEDICATED-26Dedicated P2P customer connectionsASSIGNED PAAug 7, 2008abuse@redcom.ru
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

212.19.26.0/23

Routing history

Pattern
Stable
First seen
Jul 2025
Current origin since
Jul 2025 · 1.3 yr
Origin networks
1