Data as of Nov 14, 2026

109.185.141.0/24

7 residential-proxy exits · 30 days

Moldtelecom SA

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
30
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

703 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • LightningProxies
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.185.0.0/16
since Oct 2009
AS8926Residential2,769
346 always on
Moldtelecom SA

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
109.185.0.0/1665,536MD-MOLDTELECOM-20091007Moldtelecom SA (ORG-MS14-RIPE) · MDALLOCATED PAOct 7, 2009cert.mtc@moldtelecom.md
└ 109.185.128.0/198,192MOLDTELECOM-NETJSC "Moldtelecom" S.A.ASSIGNED PAMay 20, 2010cert.mtc@moldtelecom.md
via MD-MOLDTELECOM-20091007

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

109.185.128.0/18

Routing history

Pattern
Stable
First seen
Oct 2010
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1