Channel
@tarekcloud
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
630subscribers
+1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002695687480 |
|---|---|
| Type | Channel |
| Username | @tarekcloud |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/tarekcloud |
Other / unclassifiable — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 60% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 21:38 | 630 | -1 |
| 7 Sept 2026, 06:16 | 631 | +1 |
| 30 Aug 2026, 09:43 | 630 | +2 |
| 22 Aug 2026, 09:44 | 628 | +2 |
| 14 Aug 2026, 21:24 | 626 | -3 |
| 8 Aug 2026, 02:50 | 629 | no change |
| 7 Aug 2026, 17:52 | 629 | first reading |
20 posts held, back to 10 January 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 8 July 2026. An engagement rate over an empty window would be a number about nothing.
45 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 53.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 24 | 53.3% | |
| ❤ | 9 | 20.0% | |
| 😁 | 5 | 11.1% | |
| 🆒 | 1 | 2.22% | |
| 👏 | 1 | 2.22% | |
| 💔 | 1 | 2.22% | |
| 😱 | 1 | 2.22% | |
| 🤔 | 1 | 2.22% | |
| 🤬 | 1 | 2.22% | |
| 🥰 | 1 | 2.22% |
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 11 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 45 reactions 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 January 2026 to 8 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
由于需要修复高危安全漏洞 CVE-2026-53359，我们将对虚拟化平台进行紧急安全维护，并执行主机重启操作。 维护期间，受影响的服务器可能会出现短暂中断、重启或网络暂时不可用的情况。维护完成后，您的服务将自动恢复运行。 To address the high-risk security vulnerability CVE-2026-53359, we will perform emergency security maintenance on our virtualization platform and restart the affected host machines. During the maintenance, affected servers may experience temporary service interruption, reboot, or network unavailability. Se…
❤5
维护通知/Maintenance Notice 尊敬的用户： 您好！为了提供更优质的服务，今晚 11:00 (23:00) 将对 HK（香港）地区 进行网络维护。 预计影响： 维护期间预计会造成约 15分钟 的网络中断。 请知悉并提前做好相关准备。给您带来的不便敬请谅解，感谢您的支持与配合！ Dear Users, Please be informed that network maintenance will be conducted in the HK (Hong Kong) region tonight at 11:00 PM. Expected Impact: An estimated network interruption of approximately 15 minutes will occur during the maintenance period. Please make any necessary …
❤1
【香港故障通告】 目前我们的香港区域 Gold 服务器突发电源故障，且 iDRAC 远程访问需要进行一些设置。正在处理中，完成后将第一时间恢复访问。 【最新进展 2026年5月29日 22:00（北京时间）】 经排查，本次故障的具体原因为服务器 BIOS 错误地判定功耗超限（实际双电源冗余功率完全足够），导致跳电重启并卡在 BIOS 启动引导界面。此前因 iDRAC 配置问题导致无法进行远程开机操作。 目前 iDRAC 远程控制已全面修复，服务已彻底恢复正常。为了彻底杜绝此类 BIOS 误判及冗余问题发生，我们计划在 6 月中下旬对该节点进行电源更换与升级。同时，我们将为所有受影响用户延长 2 天使用时长。 [HK Incident Notice] Our Gold server in the HK region is currently experiencing a sudden power failure, an…
❤1
HK地区路由异常通知 2026/05/19 23:20 (北京时间) 香港核心路由突发异常，检查发现疑似 VPP 层面故障，正在修复中，恢复后会在此更新动态。 2026/05/20 00:02 (北京时间) 香港网络已恢复，目前运行在冗余路由上，IPv6暂不可用，IPv4正常，为彻底解决问题，后续还将进行一次维护，对主路由系统进行维护，彻底恢复后我们将在此处更新。 2026/05/20 23:40 (北京时间) 目前正在进行主路由系统的更换与彻底维护。在此期间，网络预计会出现 15 分钟左右的中断，实际维护时长可能会根据现场情况有所调整，且期间可能会伴随数次短暂的闪断/中断。维护彻底完成后，IPv6 及整体网络将完全恢复正常，感谢您的理解与耐心等待。 HK Region Routing Anomaly Notice 2026/05/19 23:20 (UTC+8) An unexpected anomaly occurred …
❤1
#香港节点迁移完成及补偿发放通知 各位用户，🇭🇰HK机房已于 本月2日 完成IT2至Equinix HK2的迁移，因上游网络交付延迟，最终于 12日 正式通网，并于近日进一步完善。 目前网络直连T1级上游，并采用了全新架构，此外我们还部署了Anti-DDoS服务，稳定性将大大提升。 香港国际系列产品不提供中国大陆方向的网络保证。该产品线的后续定位将专注于提供高配置存储与计算服务。 💡 为补偿本次断网带来的影响，1个月的补偿时长现已全量发放到账，请注意查收。感谢大家的耐心等待！更多说明请查看邮件通知。
👍2🥰1
#香港机柜整体搬迁通知 因业务调整与机房升级需要，香港服务器将于 2026 年 3 月 29 日 由 IT2 机房 整体搬迁至 Equinix HK2 机房。 受本次迁移影响，相关服务预计会有 5–7 天 的波动或中断，最迟将于 2026 年 4 月 4 日 前恢复完成。请您提前做好相关安排。 为补偿本次迁移对您造成的影响，我们将为所有受影响用户 统一补偿 15 天 服务时长。 如迁移进度或恢复时间发生变化，我们将通过邮件持续同步，请您及时关注通知。 感谢您的理解与支持！
😁5👍4💔1🤔1🆒1
#通知 目前流媒体解锁 模式 变更为 用户自主使用模式， 您可以使用 自有DNS 进行解锁，或使用我们提供的 多地区解锁 DNS 可用地区如下（访问用户后台查看详情）： * 🇸🇬 Singapore * 🇩🇪 Germany * 🇦🇪 Dubai, UAE * 🇺🇸 Phoenix, USA * 🇯🇵 Osaka, Japan * 🇰🇷 Seoul, South Korea 只需将系统 DNS 修改为解锁DNS即可， 同时支持 IPv4 / IPv6 接入 。 注意：该服务仅限 TarekCloud 客户使用，且无可用性保证。
👍8
#通知 友好交流QQ群，993705020，有问题可以给群主留言。
#网络异常的手动修复方法 如果您在清洗网络环境下遇到下行速度异常或其他相关网络问题，建议您尝试将系统网络的 MTU 值调整为 1420 或更低后进行测试，以确认问题是否得到缓解或解决。
#新业务通告 后续会陆续接入多个地区的公司类业务，目前有美国任意州公司的注册/EIN申请/年审/报税/支付接口辅助申请等业务，如您有需求欢迎咨询。
#功能更新 官网下单逻辑已完成全面优化升级，下单流程更加流畅，带来更快的响应速度与更好的体验。
#故障通知 目前 LAX 地区网络故障，已经联系上游进行处理，最新通知请您参考用户面板详情。
Showing the 12 most recent of 20 posts we hold for @tarekcloud. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Tarekcloud Channel” (@tarekcloud), 630 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/tarekcloud.
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.