Data as of Nov 18, 2026

95.104.237.0/24

6 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address · Proxy exits nearby

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
6
100% of its exits
Providers
46
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

9.3K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • DataImpulse
  • Decodo
  • Evomi
  • FlashProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • IPFly
  • IPRoyal
  • InfiniteProxies
  • KindProxy
  • Kookey
  • Maskify
  • MoMoProxy
  • NiuProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.104.128.0/17
since Aug 2022
AS8359Mobile7,820
1,113 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
95.104.128.0/1732,768RU-MTU-20081128MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 28, 2008abuse@mtu.ru
└ 95.104.237.0/24256b2bhub-ekt-1MTS ipv4 broadband network Ekaterinburg (b2b)ASSIGNED PAFeb 8, 2023abuse@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

Summary

Routing history

Pattern
Stable
First seen
Feb 2023
Current origin since
Feb 2023 · 3.8 yr
Origin networks
1