LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

77.66.186.0/23

24 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
24
4.7% of its addresses · 30 days
Always-on exits
4
17% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
61
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

4.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.66.186.0/24418
77.66.187.0/2406

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonode
  • GloryCloud
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonPrime
  • MangoProxy
  • Maskify
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateByte
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxying
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • SwiftProxy
  • TalorData
  • Thordata
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.66.128.0/17
since Jul 2023
AS8359Mobile127
18 always on
MTS PJSC

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
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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