6 Aug 2026, 18:23 UTC17 viewsread 6 August 2026
Penalties for round 1785941768 Round started: 05.08.2026 14:56:08 UTC Round ended: 06.08.2026 09:08:24 UTC No poorly performing validators in the round
Channel
TON Status Notifications
@tonstatus_notifications
On this record: Growth · Engagement · Posts · Citations · Cite this entry
328subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002232028426 |
|---|---|
| Type | Channel |
| Username | @tonstatus_notifications |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/tonstatus_notifications |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 07:36 | 328 | -2 |
| 30 Aug 2026, 15:37 | 330 | -3 |
| 22 Aug 2026, 21:25 | 333 | -1 |
| 6 Aug 2026, 21:46 | 334 | no change |
| 6 Aug 2026, 02:21 | 334 | first reading |
Engagement
20 posts held, back to 22 July 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
6 Aug 2026, 00:03 UTC35 viewsread 6 August 2026
Penalties for round 1785876232 Round started: 04.08.2026 20:43:52 UTC Round ended: 05.08.2026 14:56:08 UTC No poorly performing validators in the round
5 Aug 2026, 05:53 UTC44 viewsread 6 August 2026
Penalties for round 1785810696 Round started: 04.08.2026 02:31:36 UTC Round ended: 04.08.2026 20:43:52 UTC No poorly performing validators in the round
4 Aug 2026, 11:43 UTC50 viewsread 6 August 2026
Penalties for round 1785745160 Round started: 03.08.2026 08:19:20 UTC Round ended: 04.08.2026 02:31:36 UTC No poorly performing validators in the round
3 Aug 2026, 17:33 UTC55 viewsread 6 August 2026
Penalties for round 1785679624 Round started: 02.08.2026 14:07:04 UTC Round ended: 03.08.2026 08:19:20 UTC No poorly performing validators in the round
2 Aug 2026, 23:42 UTC70 viewsread 6 August 2026
From July 26 through July 30, 2026, validator complaint notifications were not delivered due to an error. The issue was resolved on July 30. We apologize for the inconvenience.
2 Aug 2026, 23:22 UTC68 viewsread 6 August 2026
Penalties for round 1785614088 Round started: 01.08.2026 19:54:48 UTC Round ended: 02.08.2026 14:07:04 UTC No poorly performing validators in the round
2 Aug 2026, 05:02 UTC74 viewsread 6 August 2026
Penalties for round 1785548552 Round started: 01.08.2026 01:42:32 UTC Round ended: 01.08.2026 19:54:48 UTC No poorly performing validators in the round
1 Aug 2026, 10:52 UTC81 viewsread 6 August 2026
Penalties for round 1785483016 Round started: 31.07.2026 07:30:16 UTC Round ended: 01.08.2026 01:42:32 UTC No poorly performing validators in the round
31 Jul 2026, 16:42 UTC81 viewsread 6 August 2026
Penalties for round 1785417480 Round started: 30.07.2026 13:18:00 UTC Round ended: 31.07.2026 07:30:16 UTC Index: 52 ADNL: 05BCCA748DF734D0E6C0C7119296172597863A08794147FA66B0D25F64FF2C0B Efficiency: 0.0% Penalty: 101 TON Index: 13 ADNL: 808AC1DA8F365A5F87E6A757C6E30D37EB3D43E1111C367750A83957ED841D78 Efficiency: 67.98% Penalty: 101 TON Index: 4 ADNL: 277208C880039DB174574460EFCAC28ABB0BCE8F2330E5FB2964E8EA0A32…
30 Jul 2026, 22:32 UTC67 viewsread 6 August 2026
Penalties for round 1785351944 Round started: 29.07.2026 19:05:44 UTC Round ended: 30.07.2026 13:18:00 UTC Index: 24 ADNL: 48EE4EE43FB7AE140AA98A450B5B84A077FFC2B3058031356387BF76832FF299 Efficiency: 66.21% Penalty: 101 TON Index: 52 ADNL: 05BCCA748DF734D0E6C0C7119296172597863A08794147FA66B0D25F64FF2C0B Efficiency: 0.0% Penalty: 101 TON Index: 60 ADNL: 63CCD8826AAAACF7B0DFDC1E983BF5EABC2B54062301D78CCCF944C0FEB…
29 Jul 2026, 19:33 UTC69 viewsread 6 August 2026
Penalties for round 1785286408 Round's started: 29.07.2026 00:53:28 UTC Round's over: 29.07.2026 19:05:44 UTC No poor performing validators in the round
Showing the 12 most recent of 20 posts we hold for @tonstatus_notifications. 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.
Mentions
Named by 1 registered channel — 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“TON Status Notifications” (@tonstatus_notifications), 328 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/tonstatus_notifications.
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.