Data as of Nov 16, 2026

217.66.16.0/21

8 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
8
0.39% of its addresses · 30 days
Spread
6 of 8
/24s with at least one exit
Providers
35
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

540 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 9Proxy
  • AnyIP
  • BottingTools
  • BuyingProxy
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • InfiniteProxies
  • LudaxProxy
  • NovaProxy
  • PROXYFALL
  • PROXYSAVER
  • PROXYSCRAPE
  • PYPROXY
  • PrivateProxy
  • Proxiware
  • ProxyEmpire
  • ProxyGeo
  • PuraRoute
  • Q2IP
  • RealProxy
  • ResiProxies
  • VantageProxies
  • ZENPROXY_LITE

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.16.0/204,096RU-MTU-20030625MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PANov 10, 2014abuse@mtu.ru
└ 217.66.16.0/212,048TVT-NET"MTS" OJSCASSIGNED PAOct 3, 2005abuse@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 this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2006
Current origin since
Jan 2006 · 21 yr
Origin networks
1