Data as of Nov 10, 2026

178.206.239.0/24

6 residential-proxy exits · 30 days

PJSC 'Tattelecom'

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

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Providers
19
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

23 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.206.224.0/19
since Dec 2010
AS28840Residential2,389
7 always on
PJSC "Tattelecom"
178.206.0.0/15
since Aug 2012
AS28840Residential37,815
36 always on
PJSC "Tattelecom"
178.204.0.0/14
since Dec 2010
AS28840Residential67,134
73 always on
PJSC "Tattelecom"

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.204.0.0/14262,144RU-TATTELECOM-20100331PJSC "Tattelecom" (ORG-OT4-RIPE) · RUALLOCATED PAMar 31, 2010adm-group@tattelecom.ru
└ 178.206.224.0/204,096TATARBROADBANDNETSKazan Broad-band access poolsASSIGNED PAMar 6, 2012adm-group@tattelecom.ru
via RU-TATTELECOM-20100331

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

178.206.224.0/20

Routing history

Pattern
Stable
First seen
Mar 2019
Current origin since
Mar 2019 · 7.7 yr
Origin networks
1