Telegram RegisterThe public register of Telegram
Telegram profile photo for CSIRT IT

Channel

CSIRT IT

@csirt_it

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

1,093subscribers

+4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001327672247
TypeChannel
Username@csirt_it
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live25 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/csirt_it

Growth

1,0871,0931,0907 August 2026 — 1,089 subscribers7 August 2026 — 1,088 subscribers11 August 2026 — 1,087 subscribers14 August 2026 — 1,089 subscribers21 August 2026 — 1,090 subscribers25 August 2026 — 1,093 subscribers7 August 202625 August 2026
6 measurements spanning 18 days, net +4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 1,086–1,094 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 00:341,093+3
21 Aug 2026, 01:431,090+1
14 Aug 2026, 14:151,089+2
11 Aug 2026, 02:071,087-1
7 Aug 2026, 23:221,088-1
7 Aug 2026, 10:471,089first reading

Engagement

20 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
7.55%
avg views ÷ 1,093 subscribers
Avg views / post
82.5
20 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
20
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (5 August 20267 August 2026)
Views total1,651
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 10:47 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 5 August 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

7 Aug 2026, 09:53 UTC31 viewsread 7 August 2026

Risolta vulnerabilità in prodotti Sophos Risolta una vulnerabilità con gravità “critica” presente nei prodotti Sophos Endpoint e Sophos Home. Tale vulnerabilità, qualora sfruttata, potrebbe consentire a un utente malintenzionato di elevare i propri privilegi e/o eseguire codice arbitrario sui sistemi interessati. 🔗 https://www.acn.gov.it/portale/w/risolta-vulnerabilita-in-prodotti-sophos-1

7 Aug 2026, 09:53 UTC31 viewsread 7 August 2026

Risolte vulnerabilità in Google Chrome Google ha rilasciato un aggiornamento per il browser Chrome al fine di correggere 41 nuove vulnerabilità di sicurezza, di cui 6 con gravità “critica” e 35 con gravità “alta”. 🔗 https://www.acn.gov.it/portale/w/risolte-vulnerabilita-in-google-chrome-66

7 Aug 2026, 09:13 UTC43 viewsread 7 August 2026

Aggiornamenti per prodotti Autodesk Aggiornamenti di sicurezza Autodesk risolvono 5 vulnerabilità, di cui 4 con gravità “alta”, che interessano i prodotti AutoCAD, Civil 3D, Advance Steel e Revit. Tali vulnerabilità, qualora sfruttate, potrebbero consentire ad un utente malintenzionato di accedere ad informazioni sensibili, compromettere la disponibilità del servizio ed eseguire codice arbitrario sui sistemi interes

6 Aug 2026, 16:33 UTC80 viewsread 7 August 2026

Aggiornamenti di sicurezza per Flowise Rilasciati aggiornamenti di sicurezza per Flowise, piattaforma open source per la realizzazione di workflow basati su modelli linguistici. 🔗 https://www.acn.gov.it/portale/w/aggiornamenti-di-sicurezza-per-flowise

6 Aug 2026, 15:23 UTC88 viewsread 7 August 2026

Rilevate vulnerabilità in prodotti Zyxel Rilevate due nuova vulnerabilità con gravità “alta”, nel firmware di diversi prodotti Zyxel. Tali vulnerabilità, qualora sfruttate, potrebbero consentire ad un utente malintenzionato remoto di eseguire codice arbitrario, e/o alterare i dati, configurazioni o contenuti applicativi del sistema interessato. 🔗 https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-prodotti-zy

6 Aug 2026, 15:03 UTC88 viewsread 7 August 2026

Risolta vulnerabilità in Github Enterprise server Rilasciati aggiornamenti di sicurezza che risolvono una vulnerabilità, con gravità “alta”, in GitHub Enterprise Server, edizione on‑premises della piattaforma GitHub, progettata per ambienti aziendali con requisiti avanzati di sicurezza e conformità. Tale vulnerabilità, qualora sfruttata, potrebbe consentire ad un utente malintenzionato di eliminare file arbitrari da

6 Aug 2026, 14:23 UTC87 views1 reactionsread 7 August 2026

Risolte vulnerabilità in OpenSSL Aggiornamenti di sicurezza risolvono una vulnerabilità con gravità "alta", presente in OpenSSL, libreria open source per la crittografia e la gestione delle connessioni sicure. Tale vulnerabilità, qualora sfruttata, potrebbe consentire ad un utente malintenzionato di inviare risposte OCSP opportunamente predisposte al fine di compromettere la disponibilità del servizio sui sistemi in

😁1

6 Aug 2026, 14:13 UTC81 viewsread 7 August 2026

Rilevate vulnerabilità in prodotti IBM IBM ha pubblicato aggiornamenti di sicurezza per risolvere molteplici vulnerabilità, di cui 21 con gravità "alta", in Langflow OSS, Application Gateway Operator, QRadar e WebSphere Application Server. 🔗 https://www.acn.gov.it/portale/w/rilevate-vulnerabilita-in-prodotti-ibm

6 Aug 2026, 13:23 UTC83 viewsread 7 August 2026

Langflow: PoC pubblico per lo sfruttamento della CVE-2026-12940 Disponibile un Proof of Concept (PoC) per la vulnerabilità identificata tramite la CVE-2026-12940 presente in LangFlow, piattaforma open source che fornisce un'interfaccia visuale per la costruzione ed esecuzione di workflow basati su agenti di intelligenza artificiale. Tale vulnerabilità, qualora sfruttata, potrebbe permettere a un attaccante remoto no

6 Aug 2026, 11:53 UTC86 viewsread 7 August 2026

Rilevate nuove vulnerabilità in Jenkins Rilevate nuove vulnerabilità, di cui una con gravità “critica”, in Jenkins, noto server di automazione open source. 🔗 https://www.acn.gov.it/portale/w/rilevate-nuove-vulnerabilita-in-jenkins-2

6 Aug 2026, 11:23 UTC84 viewsread 7 August 2026

Campagna di smishing a tema GLS Questo CSIRT ha recentemente rilevato una campagna di smishing a tema GLS, perpetrata via SMS, volta a carpire dati relativi alla carta di pagamento della potenziale vittima. 🔗 https://www.acn.gov.it/portale/w/campagna-di-smishing-a-tema-gls

6 Aug 2026, 10:53 UTC89 viewsread 7 August 2026

Risolte vulnerabilità in prodotti Cisco Cisco ha rilasciato aggiornamenti di sicurezza che risolvono molteplici vulnerabilità, tra cui 5 con gravità "critica" e 11 con gravità “alta”, riguardanti vari prodotti. In particolare si evidenziano la CVE-2026-20316 che risulta attivamente sfruttata in rete e la CVE-2026-20200 per la quale è disponibile un Proof of Concept (PoC). 🔗 https://www.acn.gov.it/portale/w/risolte-v

Showing the 12 most recent of 20 posts we hold for @csirt_it. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 August 2026 — this entry's latest reading, not the date you are reading this.

“CSIRT IT” (@csirt_it), 1,093 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/csirt_it.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.