Data as of Nov 20, 2026

89.251.64.0/20

50 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
50
1.2% of its addresses · 30 days
Always-on exits
11
22% of its exits
Spread
16 of 16
/24s with at least one exit
Providers
94
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

77K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BUYPERSONALPROXY
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • CatProxies
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • HydraProxy
  • IP2WORLD
  • IPFly
  • IPMUSK
  • IPOasis
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSTPROXY_PRIME
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SOTAPROXY
  • SPYDERPROXY_BASIC
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
89.251.64.0/204,096RU-UGMK-TELECOM-20060901UGMK-Telecom LLC (ORG-UL18-RIPE) · RUALLOCATED PASep 1, 2006ripe@ugmk-telecom.ru
└ 89.251.64.0/212,048NET-1-UGMK-TELECOM-RUUGMK-Telecom networkASSIGNED PASep 8, 2006ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.72.0/23512VP-NET-6-UGMK-TELECOM-RUUGMK-Telecom: V. Pyshma ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.74.0/24256EKB-NET-2-UGMK-TELECOM-RUUGMK-Telecom: Ekaterinburg ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.75.0/24256VP-NET-7-UGMK-TELECOM-RUUGMK-Telecom: V. Pyshma ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.76.0/24256VP-NET-8-UGMK-TELECOM-RUUGMK-Telecom: V. Pyshma ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.77.0/24256SEROV-1-UGMK-TELECOM-RUUGMK-Telecom: Serov ethernet clientsASSIGNED PAJun 25, 2009ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.78.0/24256VP-NET-9-UGMK-TELECOM-RUUGMK-Telecom: V. Pyshma ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901
└ 89.251.79.0/24256EKB-NET-3-UGMK-TELECOM-RUUGMK-Telecom: Ekaterinburg ethernet clientsASSIGNED PAFeb 1, 2010ripe@ugmk-telecom.ru
via RU-UGMK-TELECOM-20060901

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
Oct 2006
Current origin since
Oct 2006 · 20 yr
Origin networks
1