24 Jun 2026, 23:36 UTC≈1,180 viewsread 7 August 2026
🔧 Network unavailability 💡 Status: resolved
Channel
Aéza - Status
@aezastatus
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,212subscribers
-8 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 | -1001874896375 |
|---|---|
| Type | Channel |
| Username | @aezastatus |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/aezastatus |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 18 September 2026 and assigned it the closest of 31 fixed categories, at 65% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 14:15 | 1,212 | -6 |
| 5 Oct 2026, 21:59 | 1,218 | -25 |
| 28 Sept 2026, 09:55 | 1,243 | +4 |
| 18 Sept 2026, 19:19 | 1,239 | +1 |
| 14 Sept 2026, 09:01 | 1,238 | -2 |
| 11 Sept 2026, 01:01 | 1,240 | +2 |
| 5 Sept 2026, 22:36 | 1,238 | +1 |
| 2 Sept 2026, 00:15 | 1,237 | +2 |
| 29 Aug 2026, 23:07 | 1,235 | +1 |
| 27 Aug 2026, 05:53 | 1,234 | +3 |
| 20 Aug 2026, 08:43 | 1,231 | +10 |
| 17 Aug 2026, 16:24 | 1,221 | +2 |
| 8 Aug 2026, 14:03 | 1,219 | -1 |
| 7 Aug 2026, 23:03 | 1,220 | no change |
| 7 Aug 2026, 15:29 | 1,220 | first reading |
Engagement
20 posts held, back to 9 March 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 24 June 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
23 May 2025, 11:44 UTC≈9,840 viewsread 7 August 2026
✅ Rack power failure: a part of USA virtual servers is down, recovery in progress. 📂 Group: USA VPS nodes 💡 Status: resolved ℹ️ Information: The problem was solved yesterday
22 May 2025, 12:39 UTC≈10,200 viewsread 7 August 2026
🔧 Rack power failure: a part of USA virtual servers is down, recovery in progress. 📂 Group: USA VPS nodes 💡 Status: resolving
15 May 2025, 12:17 UTC≈10,600 viewsread 7 August 2026
✅ Some of the virtual servers in the Moscow location are currently unavailable due to a power issue at the data center. We expect the issue to be resolved shortly by the data center team. 📂 Group: MSK VPS nodes 💡 Status: resolved ℹ️ Information: Power supply and virtual server operations have been successfully restored.
15 May 2025, 12:06 UTC≈9,150 viewsread 7 August 2026
🔧 Some of the virtual servers in the Moscow location are currently unavailable due to a power issue at the data center. We expect the issue to be resolved shortly by the data center team. 📂 Group: MSK VPS nodes 💡 Status: resolving
16 Apr 2025, 13:41 UTC≈8,970 viewsread 7 August 2026
✅ Power system failure in Moscow data center (resolved) 📂 Groups: MSK VPS nodes, MSK VPS 7950x old nodes 💡 Status: resolved
3 Apr 2025, 07:58 UTC≈10,900 viewsread 7 August 2026
🔧 Unavailability of some subnets in Germany 📂 Group: FRA VPS 25 Gbps nodes 💡 Status: resolving ℹ️ Information: A small part of the subnets are unavailable in Germany. The VPS themselves continue to work, but the internet connection on them is down. The incident is in the process of being resolved with the provider of these subnets.
25 Mar 2025, 23:06 UTC≈8,610 viewsread 7 August 2026
✅ NS2 unavailability 📂 Group: NS servers 💡 Status: resolved ℹ️ Information: The work is restored, DNS service is working normally.
25 Mar 2025, 19:44 UTC≈7,720 viewsread 7 August 2026
🔧 NS2 unavailability 📂 Group: NS servers 💡 Status: resolving ℹ️ Information: NS2 is available. Waiting for records to be updated by the upstream registrar at aezadns.com.
25 Mar 2025, 19:17 UTC≈6,610 viewsread 7 August 2026
🔧 NS2 unavailability 📂 Group: NS servers 💡 Status: resolving ℹ️ Information: DNS records from billing are updated on NS1. NS2 is unavailable.
25 Mar 2025, 18:35 UTC≈5,800 viewsread 7 August 2026
🔧 NS2 unavailability 📂 Group: NS servers 💡 Status: resolving ℹ️ Information: NS2 server is unavailable. DNS records from billing are not updated on NS servers. The incident is in the process of resolution.
21 Mar 2025, 09:46 UTC≈4,730 viewsread 7 August 2026
✅ Scheduled CPU Upgrade to Ryzen 9 9950X on Several Moscow Nodes 📂 Groups: MSK VPS nodes, MSK VPS 7950x old nodes 💡 Status: resolved ℹ️ Information: The upgrade work has been completed successfully. Upgrade of processors from Ryzen 9 7950X to Ryzen 9 9950X on server nodes in Moscow has been completed in full. All servers returned to normal operation at 6:40 Moscow time.
Showing the 12 most recent of 20 posts we hold for @aezastatus. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Aéza - Status” (@aezastatus), 1,212 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/aezastatus.
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.