Data as of Nov 14, 2026

95.104.200.0/24

8 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
8
3.1% of its addresses · 30 days
Providers
38
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.104.128.0/17
since Aug 2022
AS8359Mobile7,831
1,059 always on
MTS PJSC

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.104.128.0/1732,768RU-MTU-20081128MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 28, 2008abuse@mtu.ru
└ 95.104.200.0/212,048CMST-ULYANOVSK-2010112401Ulyanovsk CSC of Privolgsky macro branch JSC "Comstar-Region"ASSIGNED PANov 24, 2010abuse@mtu.ru
via RU-MTU-20081128

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

95.104.192.0/19

Routing history

Pattern
Stable
First seen
Aug 2022
Current origin since
Aug 2022 · 4.3 yr
Origin networks
1