Data as of Nov 17, 2026

93.187.180.0/22

8 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
97% of it

Residential-proxy exits

Proxy exits
8
0.78% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
35
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

1.1K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BottingTools
  • BuyingProxy
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • IPFly
  • IPOasis
  • IPPeak
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • PYPROXY
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • ProxyEmpire
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • VibeProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
93.187.180.0/23
since Aug 2026
AS48124Residential4MTS PJSC
via branch Stream-TV, Tver
93.187.182.0/23
since Aug 2026
AS48124Residential4MTS PJSC
via branch Stream-TV, Tver

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
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.180.0/2664comstar-r-tver-loop_brEmployee VPN AccessASSIGNED PAMay 26, 2017abuse@mtu.ru
via stream-tv-tver
└ 93.187.180.64/2732comstar-r-tver-servers-clientClient's ServersASSIGNED PAJan 18, 2010abuse@mtu.ru
via stream-tv-tver
└ 93.187.180.96 - 93.187.180.239144comstar-r-tver-NAT_PPPoE_1Employee VPN Access1ASSIGNED PAJan 18, 2010abuse@mtu.ru
via stream-tv-tver
└ 93.187.180.240/298comstar-r-tver-billServer's Bill monASSIGNED PAJan 18, 2010abuse@mtu.ru
via stream-tv-tver
└ 93.187.180.248 - 93.187.180.2547comstar-r-tver-DNSServer's DNS WEB MailASSIGNED PAJan 18, 2010abuse@mtu.ru
via stream-tv-tver
└ 93.187.181.0 - 93.187.181.254255comstar-r-tver-static-clients1Clients staticASSIGNED PANov 19, 2008abuse@mtu.ru
via stream-tv-tver
└ 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
└ 93.187.183.0 - 93.187.183.254255comstar-r-tver-clients_corpClients corpASSIGNED PAJan 18, 2010abuse@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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

1,024 addresses
TypeAddressesShareRanges
Residential99297%3
Hosting323.1%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2009
Current origin since
Jan 2009 · 18 yr
Origin networks
1