Data as of Nov 15, 2026

217.145.16.0/20

136 residential-proxy exits · 30 days

MTS PJSC

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
92% of it

Residential-proxy exits

Proxy exits
136
3.3% of its addresses · 30 days
Always-on exits
6
4.4% of its exits
Spread
2 of 16
/24s with at least one exit
Providers
82
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

44K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
217.145.30.0/24460
217.145.24.0/24276

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CROXY
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonBright
  • MangoProxy
  • MarsProxies
  • Maskify
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxio
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxying
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
217.145.24.0/22
since Feb 2022
AS31558Residential76
2 always on
MTS PJSC
217.145.30.0/24
since Dec 2025
AS31558Residential60
4 always on
MTS PJSC

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.145.16.0/204,096RU-MTU-20060710MTS PJSC (ORG-ZM1-RIPE) · RUALLOCATED PAJul 10, 2006abuse@mtu.ru
└ 217.145.19.64/2664FECITY-NETZhelGorTeleKom Dial-Up usersASSIGNED PADec 7, 2006abuse@mtu.ru
via RU-MTU-20060710
└ 217.145.19.128/2664FECITY-NETZhelGorTeleKom PPTP usersASSIGNED PADec 7, 2006abuse@mtu.ru
via RU-MTU-20060710
└ 217.145.19.192/2664FECITY-NETZhelGorTeleKom JSC (ORG-ZJ2-RIPE)ASSIGNED PAJul 12, 2006abuse@mtu.ru
└ 217.145.23.0/2732FECITY-NETZhelGorTeleKom JSC (ORG-ZJ2-RIPE)ASSIGNED PAJul 12, 2006abuse@mtu.ru
└ 217.145.23.32/2732FECITY-NETZhelGorTeleKom JSC (ORG-ZJ2-RIPE)ASSIGNED PAJul 12, 2006abuse@mtu.ru
└ 217.145.23.176/2816FECITY-NETGOTEK Enterprises Group, ZheleznogorskASSIGNED PAMay 17, 2007abuse@mtu.ru
via RU-MTU-20060710
└ 217.145.23.192/2664FECITY-NETZhelGorTeleKom subnets for interconnecting networksASSIGNED PADec 7, 2006abuse@mtu.ru
via RU-MTU-20060710

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

4,096 addresses
TypeAddressesShareRanges
Residential3,76092%7
Business3368.2%7

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2007 · 19 yr
Origin networks
2
Last change of origin
Aug 2007
Recorded history

History

Handoffs
1