Telegram RegisterThe public register of Telegram
Telegram profile photo for CloudFlare Status

Channel

CloudFlare Status

@cloudflarestatus

On this record: Topic · Growth · Engagement · Posts · Cite this entry

915subscribers

+27 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001057002180
TypeChannel
Username@cloudflarestatus
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/cloudflarestatus

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 19 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 the other topics.

Growth

888915901.57 August 2026 — 888 subscribers7 August 2026 — 888 subscribers22 August 2026 — 893 subscribers28 August 2026 — 892 subscribers6 September 2026 — 894 subscribers14 September 2026 — 897 subscribers27 September 2026 — 906 subscribers7 October 2026 — 909 subscribers22 October 2026 — 911 subscribers4 November 2026 — 908 subscribers13 November 2026 — 915 subscribers7 August 202613 November 2026
11 measurements spanning 98 days, net +27. 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 884–919 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Nov 2026, 02:21915+7
4 Nov 2026, 15:58908-3
22 Oct 2026, 14:29911+2
7 Oct 2026, 05:18909+3
27 Sept 2026, 00:16906+9
14 Sept 2026, 10:18897+3
6 Sept 2026, 16:18894+2
28 Aug 2026, 18:05892-1
22 Aug 2026, 15:25893+5
7 Aug 2026, 02:16888no change
7 Aug 2026, 02:07888first reading

Engagement

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 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, 13:06 UTC47 viewsread 7 August 2026

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…

6 Aug 2026, 11:06 UTC54 viewsread 7 August 2026

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…

6 Aug 2026, 09:06 UTC56 viewsread 7 August 2026

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…

6 Aug 2026, 05:06 UTC54 viewsread 7 August 2026

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…

5 Aug 2026, 16:06 UTC65 viewsread 7 August 2026

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…

5 Aug 2026, 16:06 UTC62 viewsread 7 August 2026

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

5 Aug 2026, 15:06 UTC56 viewsread 7 August 2026

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

5 Aug 2026, 14:06 UTC57 viewsread 7 August 2026

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…

5 Aug 2026, 13:06 UTC59 viewsread 7 August 2026

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…

5 Aug 2026, 09:06 UTC63 viewsread 7 August 2026

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…

5 Aug 2026, 08:06 UTC57 viewsread 7 August 2026

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

5 Aug 2026, 05:06 UTC63 viewsread 7 August 2026

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.

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 13 November 2026 — this entry's latest reading, not the date you are reading this.

“CloudFlare Status” (@cloudflarestatus), 915 subscribers as measured 13 November 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.