Channel
@cloudflarestatus
On this record: Growth · Engagement · Posts · Cite this entry
893subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001057002180 |
|---|---|
| Type | Channel |
| Username | @cloudflarestatus |
| Created | Between 1 May 2016 and 31 January 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/cloudflarestatus |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 15:25 | 893 | +5 |
| 7 Aug 2026, 02:16 | 888 | no change |
| 7 Aug 2026, 02:07 | 888 | first reading |
20 posts held, back to 4 August 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (4 August 2026 – 6 August 2026) |
| Views total | 1,235 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 02:16 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.
THIS IS A SCHEDULED EVENT Aug 7, 00:00 - 07:00 UTC Aug 6, 13:00 UTC Scheduled - We will be performing scheduled maintenance in WAW (Warsaw) datacenter on 2026-08-07 between 00:00 and 07:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in t…
THIS IS A SCHEDULED EVENT Aug 6, 12:00 - 15:00 UTC Aug 6, 10:10 UTC Scheduled - We will be performing scheduled maintenance in HNL (Honolulu) datacenter on 2026-08-06 between 12:00 and 15:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in…
THIS IS A SCHEDULED EVENT Aug 7, 08:00 - 14:00 UTC Aug 6, 08:50 UTC Scheduled - We will be performing scheduled maintenance in SJC (San Jose) datacenter on 2026-08-07 between 08:00 and 14:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in…
THIS IS A SCHEDULED EVENT Aug 6, 08:00 - 16:00 UTC Aug 6, 04:30 UTC Scheduled - We will be performing scheduled maintenance in SJC (San Jose) datacenter on 2026-08-06 between 08:00 and 16:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in…
THIS IS A SCHEDULED EVENT Aug 5, 16:15 UTC - Aug 8, 03:45 UTC Aug 5, 16:00 UTC Scheduled - We will be performing scheduled maintenance in MIA (Miami) datacenter between 2026-08-05 16:15 and 2026-08-08 03:45 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers con…
Aug 5, 15:09 UTC Investigating - Cloudflare is investigating issues with configuration changes for Cloudflare Web Analytics and rum beacon not taking effect or showing errors. We are working to understand the full impact and mitigate this problem. More updates to follow shortly. https://ift.tt/53gdKYn
Aug 5, 14:28 UTC Identified - The issue has been identified and a fix is being implemented. Aug 5, 14:28 UTC Investigating - Cloudflare is aware of and investigating an issue whereby customers using Gateway email lists in their DNS policies are not being enforced. No other impact is implied. More updates to follow shortly. https://ift.tt/8YRQjye
THIS IS A SCHEDULED EVENT Aug 12, 05:00 - 11:00 UTC Aug 5, 13:10 UTC Scheduled - We will be performing scheduled maintenance in IAD (Ashburn) datacenter on 2026-08-12 between 05:00 and 11:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in…
THIS IS A SCHEDULED EVENT Aug 10, 10:00 UTC - Aug 11, 06:00 UTC Aug 5, 13:00 UTC Scheduled - We will be performing scheduled maintenance in IAD (Ashburn) datacenter between 2026-08-10 10:00 and 2026-08-11 06:00 UTC. Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers…
THIS IS A SCHEDULED EVENT Aug 29, 08:55 - 11:05 UTC Aug 5, 08:57 UTC Scheduled - We will be performing scheduled maintenance on core backend database systems on 2026-08-29, in two back-to-back windows, as part of an ongoing database upgrade to improve performance, security, and reliability. 09:00–10:00 UTC — Zone & account configuration: Configuration write operations made via the Dashboard, API, or tools such as T…
Aug 5, 08:02 UTC Investigating - Cloudflare is investigating an issue where uploads for Pages and Workers Assets have reduced availability. We are working to analyse and mitigate this problem. More updates to follow shortly. https://ift.tt/wYpJPGi
Aug 5, 04:51 UTC Identified - The issue has been identified and a fix is being implemented. Aug 5, 04:34 UTC Update - We are continuing to investigate this issue. This may impact customers using China Network outside of China. Aug 5, 04:17 UTC Investigating - Cloudflare is investigating an increased Managed Challenge errors for China Network. We are working to analyse and mitigate this problem. More updates to fo…
Showing the 12 most recent of 20 posts we hold for @cloudflarestatus. 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.
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.
“CloudFlare Status” (@cloudflarestatus), 893 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/cloudflarestatus.
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.