15 measurements spanning 16 days, net -2,178. 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 29,687–32,519 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
22 Aug 2026, 10:03
30,014
-1,583
21 Aug 2026, 01:32
31,597
-10
19 Aug 2026, 22:26
31,607
-55
18 Aug 2026, 20:53
31,662
-7
17 Aug 2026, 20:13
31,669
+13
16 Aug 2026, 16:08
31,656
+335
14 Aug 2026, 22:15
31,321
-316
13 Aug 2026, 11:59
31,637
-502
12 Aug 2026, 11:54
32,139
+2
11 Aug 2026, 10:16
32,137
+9
10 Aug 2026, 10:02
32,128
-6
9 Aug 2026, 13:21
32,134
-7
8 Aug 2026, 13:42
32,141
-42
7 Aug 2026, 10:13
32,183
-9
6 Aug 2026, 22:02
32,192
first reading
Engagement
31 posts held, back to 29 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 35 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
65.3%
avg views ÷ 30,014 subscribers
Avg views / post
19,600
11 posts measured
Reaction rate
0.739%
reactions ÷ views · ER floor
Posts in window
11
of 31 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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 18 August 2026
Posts held
31 (29 June 2026 – 18 August 2026)
Views total
215,600
Reactions total
1,593
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
22 Aug 2026, 17:32 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.
What this channel posts
Photos
3
Links
19
Lifetime counters from Telegram’s own channel header, read 22 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
13,305 reactions across 31 posts, in 10 distinct kinds. The most used accounts for 36.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😢
4,795
36.0%
🔥
1,882
14.1%
😱
1,825
13.7%
❤
1,083
8.14%
🙏
1,017
7.64%
👍
924
6.94%
🎉
874
6.57%
❤🔥
459
3.45%
👏
263
1.98%
👌
183
1.38%
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 31 of the 31 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 13,305reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 29 June 2026 to 18 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.
В телеграм-каналах и на даундетекторах появились сообщения о сбоях у ряда крупных сервисов и о проблемах с питанием на московских узлах связи, включая ММТС-9. Из-за этого могут быть перебои у некоторых операторов, хостингов и популярных приложений.
Наша сеть не затронута, все регионы и сервисы работают штатно.
Если заметите проблемы с доступом к своим сервисам — скорее всего, дело в связности на стороне интернет-пр…
⚠️ Авария во Франкфурте: дата-центр восстанавливает охлаждение и питание
Зоны: de-1
Тип:❗️Major
Делимся свежей информацией с площадки:
• На третьем этаже ДЦ охлаждение восстановлено: запущены три чиллера, для подстраховки развёрнуты временные холодильные установки, на площадку везут дополнительные.
• На первом и втором этажах работы продолжаются: бригады проверяют герметичность системы и постепенно возвращают под…
⚠️ Авария во Франкфурте: что известно на данный момент
Зоны: de-1
Тип:❗️Major
Рассказываем подробно, что происходит и почему.
Что произошло
Авария случилась не на нашей площадке, а на промежуточном узле — в дата-центре Equinix FR5 во Франкфурте. Это один из крупнейших телеком-хабов Европы, и через него проходят все наши каналы связи до площадки, где размещены серверы de-1. Само оборудование с вашими данными не по…
⚠️ Обновление по инциденту
Зоны: de-1
Тип:❗️Major
По новой информации, в дата-центре произошла утечка воды. В настоящее время проводится расследование обстоятельств инцидента.
Будем публиковать обновления по мере поступления дополнительной информации.
⚠️ Обновление по инциденту
Зоны: de-1
Тип:❗️Major
Аварийная ситуация в ДЦ Equinix FR5. Недоступен коммутатор опорной сети, через который обеспечивается подключение ДЦ NTT, где размещены серверы.
✅ Инцидент закрыт
Зоны: spb-1, spb-2, spb-3, spb-4, spb-5
Тип: ❗️ Major
Работа S3 восстановлена в 16:01 мск.
Инженеры продолжают наблюдать за стабильностью работы сервиса.
🔴 Программный сбой с S3 хранилищем.
Зоны: spb-1, spb-2, spb-3, spb-4, spb-5
Тип: ❗️ Major
Возник программный сбой с S3 хранилищем.
Инженеры работают над решением проблемы.
✅ Инцидент закрыт
Зоны: spb-1, spb-2, spb-3, spb-4, spb-5
Тип: ❗️ Major
Работа S3 полностью восстановлена в 14:40 мск.
Инженеры продолжают наблюдать за стабильностью работы сервиса.
🔴 Программный сбой с S3 хранилищем.
Зоны: spb-1, spb-2, spb-3, spb-4, spb-5
Тип: ❗️ Major
Возник программный сбой с S3 хранилищем.
Все данные на месте. Инженеры работают над решением проблемы.
✅ Инцидент закрыт
Зона: global
Тип: ❗️ Major
Работы по обновлению инфраструктуры, связанные с устранением рисков критической уязвимости CVE-2026-53359 в компоненте KVM ядра Linux, успешно завершены.
Все сервисы доступны и функционируют в штатном режиме.
🙏66👍60❤22🔥17😢12🎉8😱4👌3
Showing the 12 most recent of 31 posts we hold for @timewebcloud_alerts. 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.
Citation-graph rank
Citation-graph rank — 62,418 of 1,583,249entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
BotNews @BotNews · 130,469 Telegram ranks this channel #57 of 65 here — alongside 64 others — read 20 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 22 August 2026 — this
entry's latest reading, not the date you are reading this.
“Timeweb Cloud Alerts” (@timewebcloud_alerts), 30,014 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/timewebcloud_alerts.
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.
