Data as of Nov 11, 2026

217.66.26.0/23

2 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
3
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

4 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.66.26.0/2401
217.66.27.0/2401

Proxy providers listing exits

  • Ake.net
  • IPFly
  • PuraRoute

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.66.16.0/204,096RU-MTU-20030625MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 10, 2014abuse@mtu.ru
└ 217.66.26.0/23512INTELSET_OJSC_NET3"MTS" OJSCASSIGNED PAAug 17, 2006abuse@mtu.ru
via RU-MTU-20030625

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

Who has announced 217.66.24.0/21

217.66.24.0/21

Routing history

Pattern
Stable
First seen
Apr 2007
Current origin since
Apr 2007 · 20 yr
Origin networks
1