Data as of Nov 17, 2026

217.19.210.0/24

10 residential-proxy exits · 30 days

INTERDNESTRKOM, Sovmestnoe Zakrytoe Aktsionernoe Obshchestvo

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

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Always-on exits
1
10% of its exits
Providers
56
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

4.2K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_BASIC
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HELODATA
  • HideProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.19.208.0/20
since Sep 2023
AS1547Residential550
284 always on
INTERDNESTRKOM, Sovmestnoe Zakrytoe Aktsionernoe Obshchestvo

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
217.19.208.0/204,096MD-INTERDNESTRCOM-20030124INTERDNESTRKOM, Sovmestnoe Zakrytoe Aktsionernoe Obshchestvo (ORG-JI1-RIPE) · MDALLOCATED PAJan 24, 2003mansur@idc.md
└ 217.19.208.0 - 217.19.212.2551,280IDKNET-PA-ISPAggregate for ISP Interdnestrcom.ASSIGNED PAJan 24, 2003mansur@idc.md
via MD-INTERDNESTRCOM-20030124

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
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1