Data as of Nov 19, 2026

95.104.236.0/24

8 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
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
Always-on exits
1
13% of its exits
Providers
18
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

368 observations

Proxy providers listing exits

  • 711Proxy
  • AETHYN_BASIC
  • BottingTools
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • GEEKPROXY_TURBO
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • KindProxy
  • Novada
  • Proxy302
  • PuraRoute
  • RapidProxy
  • SwiftProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.104.128.0/17
since Aug 2022
AS8359Mobile7,811
1,097 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.236.0/24256b2bhub-ryazan-1MTS ipv4 broadband network Ryazan (b2b)SUB-ALLOCATED PAJan 27, 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
Jan 2023
Current origin since
Jan 2023 · 3.8 yr
Origin networks
1