Data as of Nov 14, 2026

93.187.182.0/24

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low
Recent change
New origin Aug 2026
from AS48124 MTS PJSC, after 6.4 years unannounced

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
20
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

587 observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • BottingTools
  • BuyingProxy
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • IPOasis
  • InfiniteProxies
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • ProxyEmpire
  • Shifter
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
93.187.180.0/22
since Jan 2009
AS48124Residential7MTS PJSC
via branch Stream-TV, Tver

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
93.187.176.0/212,048RU-MTU-20080722MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 22, 2008abuse@mtu.ru
└ 93.187.180.0/221,024stream-tv-tverbranch Stream-TV, TverSUB-ALLOCATED PAMay 26, 2017abuse@mtu.ru
via RU-MTU-20080722
└ 93.187.182.0 - 93.187.182.6263comstar-r-tver-NAT_PPPoE_2Employee VPN Access2ASSIGNED PAMay 26, 2017abuse@mtu.ru
via stream-tv-tver
└ 93.187.182.63 - 93.187.182.254192comstar-r-tver-clients_bgpclients bgpASSIGNED PAJan 23, 2013abuse@mtu.ru
via stream-tv-tver

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

93.187.182.0/23

Routing history

Pattern
Stable
First seen
Jan 2017
Current origin since
Aug 2026 · 3 mo
Origin networks
1