Data as of Nov 20, 2026

217.66.148.0/22

3 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Mobile
Risk
10 / 100 · Low
Shared address

Residential-proxy exits

Proxy exits
3
0.29% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
6
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

6 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.66.149.0/2402
217.66.148.0/2401

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • EZProxies
  • IPFly
  • LudaxProxy
  • PuraRoute

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
217.66.144.0/204,096RU-MTU-20030630MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 30, 2003abuse@mtu.ru
└ 217.66.148.0/23512SPBMTSMobile TeleSystems, OJSC, MR North-West, Kaliningrad BranchASSIGNED PAJul 1, 2003abuse@mtu.ru
via RU-MTU-20030630
└ 217.66.150.0/23512SPBMTSMobile TeleSystems, OJSC, MR North-WestASSIGNED PAApr 26, 2010abuse@mtu.ru
via RU-MTU-20030630

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 this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2014
Current origin since
May 2014 · 13 yr
Origin networks
1