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

95.64.178.0/24

2 residential-proxy exits · 30 days

MTS PJSC

Announcement
95.64.128.0/17
No RPKI
Announced by
AS8359
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
22
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

734 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • EZProxies
  • Evomi
  • FlashProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • InfiniteProxies
  • Oxylabs
  • Proxiware
  • ProxyRack
  • PuraRoute
  • StrikeProxy
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.64.128.0/1732,768RU-MTU-20090424MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PASep 3, 2021abuse@mtu.ru
└ 95.64.128.0/1816,384mksbalashihiPJSC MTSSUB-ALLOCATED PAOct 4, 2021abuse@mtu.ru
via RU-MTU-20090424
└ 95.64.178.0/24256Customers_P2P_2022_34_WAN_NETMTS PJSCASSIGNED PAJun 20, 2022abuse@mtu.ru
via mksbalashihi

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
Routing timeline

Who has announced 95.64.128.0/17

95.64.128.0/17

Routing history

Pattern
Stable
First seen
Jun 2009
Current origin since
Oct 2021 · 5.1 yr
Origin networks
2
Last change of origin
Oct 2021
Recorded history

History

Handoffs
1