Telegram RegisterThe public register of Telegram
Telegram profile photo for Cloudflare 在中国频道

Channel

Cloudflare 在中国频道

@Cloudflare_CN

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

5,038subscribers

-17 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001314483878
TypeChannel
Username@Cloudflare_CN
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/Cloudflare_CN

Growth

5,0385,0555,046.56 August 2026 — 5,055 subscribers7 August 2026 — 5,055 subscribers9 August 2026 — 5,048 subscribers12 August 2026 — 5,045 subscribers16 August 2026 — 5,038 subscribers6 August 202616 August 2026
5 measurements spanning 10 days, net -17. 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 5,035–5,058 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 06:235,038-7
12 Aug 2026, 16:245,045-3
9 Aug 2026, 21:585,048-7
7 Aug 2026, 04:385,055no change
6 Aug 2026, 12:315,055first reading

Engagement

20 posts held, back to 14 January 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof 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 5 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

639 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 48.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍31148.7%
13220.7%
😱11117.4%
🔥7011.0%
🎉152.35%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 18 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 639reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 14 January 2023 to 5 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @Cloudflare_CN. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 14 January 2023 to 5 December 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

5 Dec 2025, 16:36 UTC≈14,800 views26 reactionsread 12 August 2026
Photo

Cloudflare 2025年12月5日宕机事件报告 事件概述 发生时间:2025年12月5日 08:47 UTC 恢复时间:2025年12月5日 09:12 UTC 持续时间:约25分钟 影响范围:约28%的Cloudflare HTTP流量 事件性质:因系统变更引发故障,非网络攻击或恶意活动导致 根本原因 ◆为应对本周披露的React Server Components行业级漏洞,Cloudflare尝试增加WAF缓冲区大小(从128KB增至1MB) ◆在部署过程中,团队禁用了内部测试工具以解决错误增加问题 ◆该禁用操作通过全局配置系统执行,导致FL1代理版本中触发一个存在多年的Lua代码错误 影响范围 ◆受影响客户 使用较旧的FL1代理版本、部署了Cloudflare托管规则集 ◆未受影响客户 未同时满足上述两条件、由中国网络提供服务的客户流量 技术细节 漏洞背景:为防护CVE-2025-55182漏洞,增加缓冲

17😱7🔥2

18 Nov 2025, 15:10 UTC≈18,300 views59 reactions1 Starread 12 August 2026
Photo

11.18 Cloudflare 全球网络故障 故障起点 11月18日19:20 UTC+8 受影响的服务 Access、Bot管理、CDN/缓存、仪表板、防火墙、网络、WARP、Workers等核心服务 事件进度 11月19日 03:28 故障已完全解决,所有服务恢复正常 01:44 Cloudflare服务已恢复正常运行,网络错误和延迟已恢复正常水平,工程团队继续深入调查故障原因,建议重新启用此前临时禁用的Cloudflare服务 01:14 系统恢复过程中错误和延迟水平回归正常 00:46 全球范围内错误数量持续下降,剩余错误和延迟问题正在清理中 00:27 错误和延迟情况有所改善但仍有间歇性错误报告 00:04 Bot评分服务在全球恢复过程中受到间歇性影响 11月18日 22:42 修复方案已实施,故障基本解决,团队持续监控确保所有服务恢复正常 22:34 仪表板服务已恢复,应用服务影响仍在修复

🔥25😱1511🎉8

12 Jun 2025, 20:30 UTC≈13,900 views56 reactionsread 12 August 2026
Photo

Cloudflare 服务 6.13 大规模故障 故障起点:北京时间6月13日02:19 受影响的服务 Access、WARP、浏览器隔离、浏览器渲染、Durable Objects(仅限SQLite支持)、Workers KV、实时服务、Workers AI、Stream、部分Cloudflare仪表板、Turnstile、AI Gateway、AutoRAG 事件进度 04:57 所有Cloudflare服务已恢复,现在完全正常运作 04:32 全球范围内,Cloudflare服务正在迅速恢复,WARP和Turnstile已恢复正常,核心KV服务已经恢复,依赖该服务的产品正在重新上线,预计在接下来的几分钟内将进一步恢复 03:57 Cloudflare的关键Workers KV服务因第三方服务的故障而停机,导致多个依赖该服务的产品无法使用 Cloudflare工程团队正在全力恢复服务,预计会出现间歇性错误 当前部

😱4310👍3

12 Dec 2024, 05:05 UTC≈17,300 views44 reactionsread 12 August 2026
Photo

Cloudflare推出AI审核功能:强化robots.txt策略执行 Cloudflare 近日推出AI审核功能,帮助网站管理员了解AI服务、爬虫如何访问其网站内容,并能够通过网络级防火墙(WAF)强制执行robots.txt政策,确保AI爬虫遵守网站内容访问限制 💡功能说明 通过AI审核面板,用户可以轻松查看AI爬虫访问其网站的情况,包括访问请求次数和路径概述 用户可按AI搜索引擎或爬虫分类过滤数据,并检查哪些AI服务遵守了robots.txt文件中的规则 网站管理员可以在仪表盘中查看AI爬虫对robots.txt文件的遵守情况 如果发现恶意、滥用行为,管理员可以一键在网络级别配置相应规则策略,确保AI服务商按照robots.txt策略访问网站 通过该功能,网站不仅可以声明对AI爬虫的访问限制,还能主动控制和执行这一限制,防止未经授权的数据被抓取 目前,此功能现已对所有Cloudflare用户开放可用 后续,站长还可以

👍3110😱2🔥1

2 Aug 2024, 05:10 UTC≈17,800 views26 reactionsread 12 August 2026
Photo

Cloudflare将于2024年8月5日弃用自动压缩 📜背景说明 Auto Minify(自动压缩)用于通过删除 HTML、CSS 和 JavaScript 文件中的不必要字符来精简网页内容,从而减少文件大小并提高页面加载速度。然而,随着许多网站现在在构建阶段进行代码压缩(这是现代网页开发框架推荐的做法),此功能的使用逐渐减少。此外,动态压缩 HTML 内容可能引入延迟,而 CSS 和 JavaScript 文件的压缩效果也不如预期显著。因此,Cloudflare 决定弃用 Auto Minify,以确保为用户提供现阶段最有效的解决方案。 💡建议措施 1,启用 Cloudflare 的性能测量工具以获取网站分析数据。 2,运行启用和禁用 Auto Minify 的性能测试,并在测试之间清除缓存。 3,如果禁用 Auto Minify 后网站更快,则可以继续使用禁用状态,并等待功能完全弃用 4,如果启用 Auto Minif

17👍9

3 Jul 2024, 23:36 UTC≈14,500 views27 reactionsread 12 August 2026
Photo

一键阻止AI机器人、爬虫抓取网站数据 2024年生成式人工智能的流行使得用于训练模型或运行推理的内容需求猛增,各大AI公司纷纷开发爬虫在互联网上抓取用户发布的内容,部分网站用户可能并不希望 AI 机器人访问他们的网站数据,Cloudflare为此提供选择:新增一键阻止所有爬虫的功能,面向所有用户可用 用户根据自身需要也可以自行配置防火墙规则:在网站部分页面、域名中对爬虫访问部分放行 > Bots安全设置入口 Declare your AIndependence: block AI bots, scrapers and crawlers with a single click #AI #Crawler #Block Via @Cloudflare_CN

👍261

27 Jun 2024, 11:25 UTC≈12,400 views39 reactionsread 12 August 2026
Photo

注意 polyfill JS库使用风险 💡起因 polyfill.js 是一个为旧版浏览器改善兼容性的JS库被各方广泛采用(全网约4%的网站引用它),相关域名 polyfill.io 于今年2月由服务商 Funnull(方能) 接管,项目作者2月26日申明不曾拥有该域名控制权,新的服务商存在篡改JS库历史:注入恶意代码,将用户重定向跳转到其它网站,现已被各方标注不可信恶意域名 🏷措施 Cloudflare已为polyfill创建镜像同时为所有免费用户默认启用替换服务:将网页中找到的 polyfill.io 链接重写为 cdnjs.cloudflare.com/polyfill/ 以此过渡,付费用户需前往安全设置中自行启用 对于未使用Cloudflare CDN服务的朋友,在此强烈建议删除对 polyfill.io 的引用,更换使用安全的镜像备份或自行托管 polyfill.js Automatically replacin

👍2910

1 May 2024, 01:31 UTC≈13,000 views31 reactionsread 12 August 2026
Photo

Workers AI LLM Playground 在线体验主流开源大模型 💡简介 无需登录注册,在线体验三十余款主流开源模型:llma2/3、mistral、tinyllama、starling、qwen、openchat 等,最高支持 2048 Tokens 输出长度 🔗 体验入口 | 开发文档 #Workers #AI #LLM #开源 #模型 #测试 Via @Cloudflare_CN

👍292

12 Apr 2024, 15:56 UTC≈13,000 views21 reactionsread 12 August 2026
Photo

Let's Encrypt 证书链变更 💡缘由 Let's Encrypt是一家公共信任的证书颁发机构(CA),Cloudflare采用它来颁发通用TLS证书,它的证书使用了两条不同的证书链:一条与 IdenTrust 进行交叉签名(起源2000年,为老旧设备所信任,兼容性更好),另一条是Let's Encrypt自己的根CA:ISRG Root X1,在2024年9月30日后与IdenTrust的交叉签名将到期,在交叉签名到期后,将只能使用由ISRG Root X1签发的证书,大多数于2016年后发布的设备和浏览器版本不会受到此变化的影响 🏷措施 Let's Encrypt的交叉签名链将于2024年9月30日到期,Cloudflare将继续为所有Let's Encrypt证书提供IdenTrust的交叉签名链证书,直到2024年9月9日 任何专门选择了Let's Encrypt作为其CA的用户都将收到一封电子邮件通知,其

👍14🎉43

2 Nov 2023, 16:20 UTC≈16,200 views53 reactionsread 12 August 2026
Photo

Cloudflare 管理面板以及API服务故障不可用 事发 北京时间11月2日晚上19:40分前后,陆续有多人反馈Cloudflare管理面板以及API服务不可用,API响应错误提示 504、1020、10000 影响 Logpush、WARP/零信任设备状态、管理面板、API服务、Stream API、Workers API、警报通知等系统 *未受影响部分: CDN、Magic Transit、Argo 智能路由、Workers KV、WAF、速率限制、规则(更新)、 WARP / 零信任注册、等候室、负载平衡和运行状况检查、Pages、零信任网关、DNS 权威和辅助、隧道、Workers KV 命名空间操作、Magic WAN、图片存储处理分发服务 进度 11月2日(UTC+8) 19:54 宣告事件已知 20:07 确认API以及API相关联的服务不可用 20:33 着手调查事故原因 21:18 调查排查事

🔥27👍14😱93

29 Sept 2023, 02:05 UTC≈13,000 views29 reactionsread 12 August 2026
Photo

Cloudflare Snippets 即将公测可用 Cloudflare 陆续推出了许多开箱即用的产品功能、应用规则来满足客户对 HTTP 请求一般场景的简易控制,但有时候用户可能需要基于多个变量、复杂因素组合创建不同会话请求,此时标准化失效,用户需要更为灵活自主、可编程的控制为此推出 Snippets :在请求回源以前,用户可通过 Snippets 在规则集处理阶段自主编程控制请求回源规则 使用限制 Free、Pro、Biz、Ent 用户 每域名可创建 5、10、25、50 个 Snippets 单个执行时间≤5ms,内存≤2MB,大小≤32KB *Workers 按请求量计费,Snippets 为无限量免费可用 Cloudflare Snippets is now available in alpha #Cloudflare #Snippets Via @Cloudflare_CN

👍281

29 Sept 2023, 01:00 UTC≈10,600 viewsread 12 August 2026
Photo

Cloudflare Stream 最近更新 💡支持资源定时自动删除 支持为 Cloudflare Stream 上资源设置定时(指定时间)以及倒计时(按天)两种自动删除方式,简化用户资源存储管理并帮助用户降低使用成本 Introducing scheduled deletion for Cloudflare Stream 💡开放低延迟HTTP直播流 (LL-HLS)所有人可用 Cloudflare Stream Low-Latency HLS support now in Open Beta #Cloudflare #Stream #HLS #Live #更新 Via @Cloudflare_CN

Showing the 12 most recent of 20 posts we hold for @Cloudflare_CN. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 597,646 of 1,549,376entries 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.

Forward network

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.

Mentions

Named by 2 registered channels — 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“Cloudflare 在中国频道” (@Cloudflare_CN), 5,038 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Cloudflare_CN.

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.