Data as of Nov 21, 2026

77.66.180.0/24

3 residential-proxy exits · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
37
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

2.2K observations

Proxy providers listing exits

  • AETHYN_ELITE
  • BUYPERSONALPROXY
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HPROXY
  • HideProxy
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSAVER
  • PROXYSCRAPE
  • PYPROXY
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.66.128.0/1732,768RU-MTU-20070125MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJan 25, 2007abuse@mtu.ru
└ 77.66.177.0 - 77.66.183.2551,792ROSTOV-GSPD-NETIP address space for Rostov-on-Don Regional Data exchange NetworkASSIGNED PAJul 29, 2008abuse@mtu.ru
via RU-MTU-20070125

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 77.66.128.0/17

77.66.128.0/17

Routing history

Pattern
Reactivated
First seen
Feb 2007
Current origin since
Jul 2023 · 3.3 yr
Origin networks
2
Last change of origin
Jul 2023
Recorded history

History

Handoffs
1