Data as of Nov 18, 2026

212.19.30.0/24

35 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
35
14% of its addresses · 30 days
Always-on exits
1
2.9% of its exits
Providers
38
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

3.1K observations

Proxy providers listing exits

  • 9HTTP
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • HASDATA
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • Infatica
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential438
57 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.30.0/24256REDCOM-BB-4REDCOM Broadband Block 4ASSIGNED PAJan 24, 2013abuse@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.28.0/22

Routing history

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