Data as of Nov 16, 2026

217.23.183.0/24

7 residential-proxy exits · 30 days

PJSC 'Tattelecom'

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Providers
43
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • FlashProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • LUMIPROXY
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.23.176.0/21
since Feb 2009
AS28840Residential14
1 always on
PJSC "Tattelecom"
217.23.176.0/20
since May 2005
AS28840Residential754
2 always on
PJSC "Tattelecom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.23.176.0/204,096RU-TATTELECOM-20030303PJSC "Tattelecom" (ORG-OT4-RIPE) · RUALLOCATED PAMar 3, 2003adm-group@tattelecom.ru
└ 217.23.176.0/212,048TATTELECOMISP TATTELECOM, Russian Federation, city KazanASSIGNED PAMar 4, 2003adm-group@tattelecom.ru
via RU-TATTELECOM-20030303

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

Covering aggregate above, the prefix's own history below

217.23.182.0/23

Routing history

Pattern
Stable
First seen
Feb 2022
Current origin since
Feb 2022 · 4.7 yr
Origin networks
1