Channel
@cnfasterchannel
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,014subscribers
+0 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002273269436 |
|---|---|
| Type | Channel |
| Username | @cnfasterchannel |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/cnfasterchannel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 18:25 | 1,014 | no change |
| 14 Aug 2026, 12:33 | 1,014 | first reading |
20 posts held, back to 10 July 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 pageof 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 30 October 2025. An engagement rate over an empty window would be a number about nothing.
225 reactions across 16 posts, in 16 distinct kinds. The most used accounts for 54.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 122 | 54.2% | |
| ❤ | 25 | 11.1% | |
| 🤡 | 17 | 7.56% | |
| 👏 | 16 | 7.11% | |
| 😁 | 11 | 4.89% | |
| 😢 | 7 | 3.11% | |
| 🔥 | 6 | 2.67% | |
| 👍 | 4 | 1.78% | |
| 😭 | 4 | 1.78% | |
| 🙏 | 4 | 1.78% | |
| ✍ | 2 | 0.889% | |
| 👎 | 2 | 0.889% | |
| 🤔 | 2 | 0.889% | |
| 🌚 | 1 | 0.444% | |
| 😈 | 1 | 0.444% | |
| 😱 | 1 | 0.444% |
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 17 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 225reactions 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 10 July 2025 to 30 October 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.
尊敬的用户您好。 CNFaster HK区域因Stripe时间太久无法正常原路退回。目前仅支持支付宝退回。 请在 https://www.wjx.cn/vm/eZtuTC8.aspx 中填写信息。 其中如有多台主机，请多次分开填写，以便统计。 支付宝仅需填写邮箱或手机号即可。 Q：为什么不支持支付宝扫码退款而是要实名信息？ A：因为支付宝扫码退款依旧可以获取实名信息，所以对于用户而言没有区别。 Q：那我不想这样怎么办 A：可以私聊 @AS152672 进行查询是否可以原路退回，提供主机名和邮箱即可。如无法原路退回我方可以提供退回至支付宝扫码或余额
❤1
Update：目前CNFaster支付宝快速退款已经全部完成。之后的退款原路请填写表格 https://www.wjx.cn/vm/QOvdHCn.aspx# ，其他支付宝支付方式请等待通知。 现在支付宝未到账的请联系 @AS152672 进行核对。感谢您的支持。
👍2
Update:HK业务将于10/25 12:00正式结束。机器将在一日内全部清除。请尽快做出数据备份。 10/25 18:00 将提供新的Stripe原路退回通道。提交主机名即可等待原路退回处理。 其余退费疑问请于10/25 18:00 联系 @AS152672 一并处理。
💩22🤡3
Update： https://www.wjx.cn/vm/eZtuTC8.aspx 发这里吧各位 不发的25日后stripe退款 发了的机器删除后会记录退款具体金额，等待批量付款即可。
💩16✍2
Update：请提供支付宝手机号或邮箱与姓名，我方将批量处理，而不是通过二维码。谢谢。
💩9
因stripe时间久远订单无法退款，请各位联系 @AS152672 发送主机名 邮箱 支付宝手机号或邮箱 与实名 到账户。未回复无需重新发送，会在第一时间全部处理。 此次HK地区 我方预估错了客户的需求，导致无法弥补成本亏损。抱歉。
💩22😭4🙏4🤡3
很抱歉。CNFaster的线路决定无法承受DDoS的流量攻击，以至于近几月无法提供稳定的服务。 我方将于近日清退所有Personal套餐。 请立即开始备份数据。 如有收来的服务器请联系 @AS152672 单独申请退款。（提供邮箱 主机名 支付宝二维码） 其他套餐用户等待下一步通知。
💩44😢6👏5🤡2🌚1😁1😱1
https://www.nodeseek.com/post-455978-1
尊敬的用户您好，目前艾云遭受严重的DDoS攻击，受影响区域为洛杉矶绝大部分机器。我方已经启用防御但仍然无法完全清洗流量。近期出现不稳定我方深表抱歉。
🌟 HKLite-Pro Storage – 大宽带大存储产品，大盘用户优选！ 💰 续费仅 340 HKD/年 🔹 2 vCPU | 2GB RAM （开通自动再送 2GB 内存） 🔹 20GB SSD | RAID 数据保护 （设置费20，续费不收取） 🔹 1000GB ESSD（SSD缓存的HDD） | RAID 数据保护 （设置费120/T，续费不收取） 🔹 5000GB@5Gbps（开通自动再送 3000GB 流量） 🔹 适合大盘用户 🔥 立即购买 👉 点击购买 HKLite-Pro Storage 本次大盘因存量较少，仅100T左右，如超过存量则会进入预售模式，半个月内完成新的存储设备采购+上架。 记得手动添加数据盘哦
❤3
今日会上架大盘服务器，目前因磁盘仅130T左右可用，故本次销售会按顺序开通，其他未开通的会有半个月左右的设备采购时间。
👏9💩5🤡4❤1
例行维护： 2025/8/14 21:00左右（因施工问题，于8/15 0:30开始） 升级跨机房间传输至100G独立链路
😁8😈1
Showing the 12 most recent of 20 posts we hold for @cnfasterchannel. 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 — 1,432,638 of 1,548,671entries 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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.
“CNFaster 墙速” (@cnfasterchannel), 1,014 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/cnfasterchannel.
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.