Data as of Nov 14, 2026

77.66.187.0/24

6 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
33
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

1.0K observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • GSocks
  • GloryCloud
  • IPFly
  • IPRoyal
  • Infatica
  • KindProxy
  • MangoProxy
  • Maskify
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.66.128.0/17
since Jul 2023
AS8359Mobile126
14 always on
MTS PJSC

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.186.0/23512MTS-TATIP address space for KazanASSIGNED PAMar 3, 2026abuse@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

Covering aggregate above, the prefix's own history below

77.66.186.0/23

Routing history

Pattern
Stable
First seen
Mar 2021
Current origin since
Sep 2024 · 2.2 yr
Origin networks
1