Channel
@hiddencestatus
On this record: Growth · Engagement · Posts · Citations · Cite this entry
22subscribers
+2 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002730516934 |
|---|---|
| Type | Channel |
| Username | @hiddencestatus |
| Created | Between 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 28 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 28 August 2026 |
| On Telegram | t.me/hiddencestatus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 19:33 | 22 | +2 |
| 11 Aug 2026, 16:01 | 20 | no change |
| 8 Aug 2026, 01:49 | 20 | first reading |
20 posts held, back to 10 November 2025 — 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 3 June 2026. An engagement rate over an empty window would be a number about nothing.
⚠️ On June 4, from 00:00 to 01:00 UTC, scheduled maintenance will be carried out on the Client Area and the Telegram bot. During this hour, both the website and the Telegram bot will be completely unavailable. ✔️ The services will not be affected — all servers will continue running as usual.
Problem solved.
We've been notified of network issues on EPYC nodes. We're currently working on a fix.
New IP addresses have been added and service orders are now available!
New orders are temporarily unavailable due to a lack of IP addresses. We will be adding new prefixes soon.
The issues with EPYC nodes have been resolved. All clients on AMD EPYC nodes have been compensated with a service lease extension. P.S. The issue was network-related. VPS states were preserved (i.e., services were not rebooted).
Notified about issues with AMD EPYC based servers, issue is being resolved.
The issue with the node has been resolved.
Issues are being observed on one of the nodes. Already in the process of being resolved.
Problem fixed — the website and Telegram bot are back online.
There are issues with the availability of the website and Telegram bot. Client services are operating normally. We are working on resolving it.
The issue has been resolved — all services are now fully operational. We'll update this post shortly with an explanation of what caused the problem.
Showing the 12 most recent of 20 posts we hold for @hiddencestatus. 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 — 494,510 of 1,629,452 entries 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.
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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Hiddence: Status” (@hiddencestatus), 22 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/hiddencestatus.
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.