LAYER3 INTEL
Get started
Sign in
Data as of Nov 9, 2026

95.175.224.0/19

5 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
AS30881
Type
Residential

Residential-proxy exits

Proxy exits
5
0.06% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
5 of 32
/24s with at least one exit
Providers
16
selling exits here
Oct 10, 2026 – Nov 8, 2026

Exits seen per day

580 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.175.246.0/2411
95.175.226.0/2401
95.175.232.0/2401
95.175.239.0/2401
95.175.252.0/2401

Proxy providers listing exits

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

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
95.175.224.0/21
since Oct 2019
AS30881Residential1MTS PJSC
95.175.232.0/21
since Oct 2019
AS30881Residential2MTS PJSC
95.175.240.0/21
since Oct 2019
AS30881Residential1
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.224.0/24256TensorTelecom-NetworkClient UplinksASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.225.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.226.0/24256TensorTelecom-NetworkClient UplinksASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.227.0/24256TENSORTELECOM-NETWORKunknownASSIGNED PAApr 4, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.228.0/221,024TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAApr 4, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.232.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.233.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.234.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.235.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.236.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.237.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.238.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.239.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 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
└ 95.175.248.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.249.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.250.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.251.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.252.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.253.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.254.0/24256TENSORTELECOM-NETWORKPPPoE and PPTP clientsASSIGNED PAJun 2, 2017abuse@mtu.ru
via RU-MTU-20090408
└ 95.175.255.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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Origin network

AS30881

RU
Name
MTS PJSC
Type
Internet provider
Registered
Jan 5, 2004
Domain
mts.ru
Industry
Computer and Information Technology
Spamhaus ASN-DROP
not listed