Data as of Nov 15, 2026

217.23.176.0/23

1 residential-proxy exit · 30 days

PJSC 'Tattelecom'

Announcement
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
19
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

425 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.23.176.0/20
since May 2005
AS28840Residential754
2 always on
PJSC "Tattelecom"
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
217.23.177.0/24
since Apr 2024
AS28840ResidentialPJSC "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.176.0/21

Routing history

Pattern
Stable
First seen
Feb 2009
Current origin since
Feb 2009 · 18 yr
Origin networks
1