Data as of Nov 10, 2026

5.2.40.0/22

15 residential-proxy exits · 30 days

UGMK-Telecom LLC

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

Residential-proxy exits

Proxy exits
15
1.5% of its addresses · 30 days
Always-on exits
4
27% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
46
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

4.0K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
5.2.42.0/2425
5.2.40.0/2414
5.2.41.0/2413
5.2.43.0/2403

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

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
5.2.32.0/198,192RU-UGMK-TELECOM-20111201UGMK-Telecom LLC (ORG-UL18-RIPE) · RUALLOCATED PAApr 27, 2012ripe@ugmk-telecom.ru
└ 5.2.40.0/221,024Siberian-Reg-Net-10UGMK-Telecom networkASSIGNED PAMay 10, 2012ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20111201

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1