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

217.65.211.0/24

8 residential-proxy exits · 30 days

MTS PJSC

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
40
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

3.4K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CROXY
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • Geonode
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPRoyal
  • KindProxy
  • Kookey
  • LUMIPROXY
  • NSocks
  • NextProxy
  • NiuProxy
  • Novada
  • Oxylabs
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • ZENPROXY_PREMIUM

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.65.208.0/204,096RU-MTU-20030624MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJun 24, 2003abuse@mtu.ru
└ 217.65.208.0 - 217.65.213.2551,536OVERTA-NETTC Overta Ltd.ASSIGNED PAJun 24, 2003abuse@mtu.ru
via RU-MTU-20030624

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 217.65.208.0/20

217.65.208.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1