Data as of Nov 17, 2026

212.19.18.0/24

2 residential-proxy exits · 30 days

JSC 'Redcom-lnternet'

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
23
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

2.1K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FloppyData
  • GonzoProxy
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • Thordata
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
212.19.0.0/19
since May 2005
AS8749Residential437
56 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
212.19.0.0/198,192RU-REDCOM-980323JSC "Redcom-lnternet" (ORG-RA23-RIPE) · RUALLOCATED PA—abuse@redcom.ru
└ 212.19.18.0 - 212.19.18.111112REDCOM-KMS-BACKBONEREDCOM Backbone network in Komsomolsk-on-AmurASSIGNED PAApr 6, 2017abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.18.112/298REDCOM-CLNT-KMS-ELCOM-SvyazunknownASSIGNED PAApr 6, 2017abuse@redcom.ru
via RU-REDCOM-980323
└ 212.19.18.128/25128REDCOM-BB-KMS-1REDCOM Broadband Block 1 on Komsomolsk-on-AmurASSIGNED PAApr 6, 2017abuse@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

Summary

Routing history

Pattern
Stable
First seen
Jan 2008
Current origin since
Nov 2016 · 10 yr
Origin networks
1