Data as of Nov 10, 2026

95.129.149.0/24

9 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
1
11% of its exits
Providers
26
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • AnyIP
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • Evomi
  • FloppyData
  • Geonode
  • IPFly
  • InfiniteProxies
  • NSocks
  • NodeMaven
  • PrivateByte
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxmint
  • Proxy-Cheap
  • Proxy4U
  • ProxyEmpire
  • PuraRoute
  • Shifter
  • Thordata
  • VibeProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.129.144.0/21
since Nov 2010
AS42087Residential43
3 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.129.144.0/212,048RU-MTU-20101006MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAOct 6, 2010abuse@mtu.ru
└ 95.129.148.0/221,024ru-kanal7CJSC Cannel-7ASSIGNED PAOct 17, 2011abuse@mtu.ru
via RU-MTU-20101006

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.129.148.0/22

Routing history

Pattern
Stable
First seen
Oct 2017
Current origin since
Oct 2017 · 9.1 yr
Origin networks
1