Data as of Nov 20, 2026

212.19.5.0/25

No anonymizer space · no proxy exits in 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
9
7.0% of its addresses · listed by providers
Always-on exits
2
22% of its exits
Providers
37
selling exits here

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CliProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyStyler
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential441
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.5.0/25128REDCOM-DEDICATED-5Dedicated P2P customer connectionsASSIGNED PADec 23, 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.4.0/22

Routing history

Pattern
Stable
First seen
Oct 2008
Current origin since
Jul 2025 · 1.4 yr
Origin networks
1