Data as of Nov 17, 2026

95.175.240.0/21

1 residential-proxy exit · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 8
/24s with at least one exit
Providers
17
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

440 observations

Proxy providers listing exits

  • ASHBURNPROXIES
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Decodo
  • FlashProxy
  • FlexyProxies
  • IPFly
  • PROXYSCRAPE
  • Proxio
  • Proxiware
  • ProxyRack
  • PuraRoute
  • StrikeProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.175.224.0/19
since Apr 2009
AS30881Residential6
1 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.175.224.0/198,192RU-MTU-20090408MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAApr 8, 2009abuse@mtu.ru
└ 95.175.240.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.241.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.242.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.243.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.244.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.245.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.246.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.247.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408

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
Oct 2019
Current origin since
Oct 2019 · 7.1 yr
Origin networks
1