【网络拥塞通知】 目前,Cogent 与中国移动国际互联线路再次出现拥塞,Cogent ISP 产品可能发生间歇性丢包、延迟升高及速率下降。 该问题源于上游运营商跨境出口负载过高,目前暂时无法由我们直接解决。相关扩容及线路调整周期较长,我们将持续关注网络状态。 由此带来的不便,敬请谅解。 ZoroCloud 运维团队
🤡12😐3

Channel
@zoro_notice
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
2,957subscribers
+714 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002588968206 |
|---|---|
| Type | Channel |
| Username | @zoro_notice |
| 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 | 7 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/zoro_notice |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 05:26 | 2,957 | +41 |
| 4 Nov 2026, 06:40 | 2,916 | +31 |
| 1 Nov 2026, 15:30 | 2,885 | +47 |
| 29 Oct 2026, 17:59 | 2,838 | +29 |
| 26 Oct 2026, 16:16 | 2,809 | +43 |
| 23 Oct 2026, 12:48 | 2,766 | +26 |
| 20 Oct 2026, 13:26 | 2,740 | +34 |
| 17 Oct 2026, 02:55 | 2,706 | +41 |
| 14 Oct 2026, 00:09 | 2,665 | +51 |
| 8 Oct 2026, 22:16 | 2,614 | +23 |
| 2 Oct 2026, 12:57 | 2,591 | +96 |
| 16 Sept 2026, 20:56 | 2,495 | +25 |
| 13 Sept 2026, 06:59 | 2,470 | +28 |
| 9 Sept 2026, 12:16 | 2,442 | +36 |
| 4 Sept 2026, 10:17 | 2,406 | +39 |
| 31 Aug 2026, 20:24 | 2,367 | +7 |
| 29 Aug 2026, 03:01 | 2,360 | +9 |
| 25 Aug 2026, 23:56 | 2,351 | +19 |
| 23 Aug 2026, 09:48 | 2,332 | +9 |
| 20 Aug 2026, 05:25 | 2,323 | first reading |
20 posts held, back to 11 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
141 reactions across 17 posts, in 14 distinct kinds. The most used accounts for 22.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 31 | 22.0% | |
| ❤ | 28 | 19.9% | |
| 💩 | 20 | 14.2% | |
| 👎 | 19 | 13.5% | |
| 🤡 | 18 | 12.8% | |
| 😱 | 6 | 4.26% | |
| 🤬 | 6 | 4.26% | |
| 😐 | 3 | 2.13% | |
| 👌 | 2 | 1.42% | |
| 😁 | 2 | 1.42% | |
| 🤮 | 2 | 1.42% | |
| 🤯 | 2 | 1.42% | |
| 🕊 | 1 | 0.709% | |
| 🥰 | 1 | 0.709% |
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 141 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 11 January 2026 to 6 August 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.
【网络拥塞通知】 目前,Cogent 与中国移动国际互联线路再次出现拥塞,Cogent ISP 产品可能发生间歇性丢包、延迟升高及速率下降。 该问题源于上游运营商跨境出口负载过高,目前暂时无法由我们直接解决。相关扩容及线路调整周期较长,我们将持续关注网络状态。 由此带来的不便,敬请谅解。 ZoroCloud 运维团队
🤡12😐3
服务器迁移公告-38.84.XX.XX 迁移时间: 2026年8月4日 23:00(北京时间) 影响说明: 迁移期间,该服务器相关服务可能出现短暂中断或无法访问。迁移完成后,服务器 IP 地址将发生变化。请前往后台自助刷新获取新 IP。 ZoroCloud 运维团队 已处理
🤬6❤2
【维护公告】美国GTT 网络维护通知 维护时间:2026年7月26日(星期日)06:00–07:00(北京时间) 预计影响:维护期间服务器可能重启,业务预计中断约15分钟。 受影响网段:66.253.XX.XX 请受影响用户提前做好数据保存及业务安排。维护完成后,相关服务将自动恢复,无需进行额外操作。 ZoroCloud 运维团队 已恢复
KVM 安全维护公告-KVM Guest-to-Host Escape 为修复 CVE-2026-53359(Januscape)逃逸漏洞,将于 2026 年 07 月 08 日 00:00 开始对所有服务器进行陆续重启维护,预计 2026 年 07 月 09 日 06:00 前全部完成。 2026 年 07 月 08 日 22:00——计划已经陆续安排实施中,实际比原定计划略微提前,机器出现关机状态是正常现象,等待自然启动即可。 已完成,机器等待陆续启动即可,如机器一直未开启,可后台自助点一下开机。
👍7❤2
香港 CN2 迁移升级公告 香港 CN2 118.107.xx.xx 段服务器将于 7 月 7 日 12:00 至 7 月 10 日陆续迁移升级。 本次迁移正常情况下不影响使用。 迁移完成后,请在后台刷新新的 IP 信息即可。 升级内容:CPU,带宽,线路升级 已完成,后台刷新IP地址即可。
【美国Cogent 网络异常通知】 上游 ISP(Cogent)与中国联通、中国移动互联节点发生拥塞,导致部分用户访问出现延迟升高、速度变慢或间歇性波动
新加坡 ISP 正在进行网络割接维护,预计 1–2 小时内完成。 维护期间可能出现网络波动或短暂中断,完成后将自动恢复正常 延迟了。仍在处理中。恢复后统一补偿时效。 已恢复! 非常抱歉!😐 ~维护出现了一些小小的意外,导致延迟了2小时,所有用户补偿7天“时效”!
❤4👎3😱2👌1
【网络使用提醒】 近期有反馈时不时断网、连接不稳定。 先自查一下是不是用了 microsoft.com SNI ,如果是的话,换一个吧。 PS:服务器一点问题没有,不要甩锅机器啦,自行检查下搭建的项目问题吧 👍👍
👍6❤1
【维护通知】日本 ISP 机器网络调整 日本 ISP 机器 运营商预计将于 2026/06/26 10:00 - 12:00 进行网络割接、维护调整。维护期间可能会出现短暂~网络中断,完成后将自动恢复正常 已完成
❤2
📢 新加坡原生双 ISP 住宅 IPv4 上线 新加坡本土电信运营商 双 ISP 住宅级线路|家宽原生双 ISP|独享静态住宅 IPv4|IP 纯净度高|适用于 TikTok、直播,店铺运用,跨境电商,Whatapp,Shopee,ChatGPT、Claude、Gemini、流媒体、游戏等业务与AI 等访问场景
👍10💩6🕊1
📢 网络情况通知 目前观察到 Cogent 与中国电信国际互联出现拥塞,部分时段可能存在延迟升高的情况。 已恢复正常
😱4😁2
⚠️ 紧急通知:Nezha Monitor(哪吒监控)安全漏洞的风险 近期大量服务器因安装 Nezha Monitor(哪吒监控)出现安全问题,导致机器被植入木马、病毒等问题产生异常,并触发上游运营商 Abuse 投诉。 请所有安装过 Nezha Monitor(哪吒监控)的用户立即处理: ✅ 请立即停止使用Nezha Monitor,并重装系统! ✅ 删除所有 Nezha 相关组件 ✅ 更换服务器密码及密钥 为避免进一步风险,请勿继续使用 Nezha Monitor!请勿继续使用 Nezha Monitor!请勿继续使用 Nezha Monitor! 特别提醒: 因 Nezha 相关安全问题导致服务器产生 Abuse 投诉、被封禁、停机或删除的,我们将不再提供恢复、解封或申诉服务。
👍5🤮2🤯2❤1
Showing the 12 most recent of 20 posts we hold for @zoro_notice. 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“ZORO|索隆云|我找到路了” (@zoro_notice), 2,957 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/zoro_notice.
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.