流量轉發 入口已恢復!
Channel
🌜半月灣🌛 NOC 及其它
@hmbcloud_noc
On this record: Topic · Growth · Engagement · Posts · Cite this entry
313subscribers
+2 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 | -1001769963000 |
|---|---|
| Type | Channel |
| Username | @hmbcloud_noc |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 2 times, most recently 7 October 2026 |
| On Telegram | t.me/hmbcloud_noc |
Topic
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 22 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 03:00 | 313 | +2 |
| 13 Sept 2026, 11:42 | 311 | +1 |
| 6 Sept 2026, 05:00 | 310 | -1 |
| 23 Aug 2026, 02:57 | 311 | +1 |
| 15 Aug 2026, 18:12 | 310 | -1 |
| 8 Aug 2026, 07:46 | 311 | no change |
| 7 Aug 2026, 09:11 | 311 | first reading |
Engagement
20 posts held, back to 20 March 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 30 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
流量轉發因運營商故障而離綫,正在處理當中,恢復后會立即通知.
流量轉發-入口恢復通知 入口已經恢复. 如在前置機填寫了"欲转发至的远程IP"(半月灣入口ip) 請保證填寫的ip為入口域名的最新ip
流量轉發-入口離綫通知 目前入口因受攻擊而離綫,预计近几天内恢复.
部分服務器于30日下午出現異常離綫 已經緊急處理完成 離綫原因為程序異常所致(非性能問題) 一般很少出現此類問題 提醒各位用戶 應注意備份您服務器中的所有重要數據 有備無患
注意事項
使用方法
流量轉發部分用戶工單反應的問題,已經和機房共同處理完成,你的規則現在應該工作正常,如有問題 可發送工單進行反饋
維護結束 入口已經恢復 請嘗試連接 如有問題 可工單反饋
受機房高防流量篩選影響 目前香港/新加坡等綫路被阻斷 今天將進行更新維護 預計明日恢復正常.
近期有工單反應,已經設置好了前置,仍然無法進行連接. 請注意 流量轉發禁止使用http 以及各類代理協議,如ssr openvpn pptp vmess v2ray等. 由於機房管理嚴格,我們限制了此類流量,該類流量無法轉發. 如果你轉發ssh流量正常,而轉發其他不正常,那麽你的協議即為被禁止的協議 禁止的協議你將無法進行連接.
三線版流量轉發-上海入口恢复通知 目前只接受固定ip進行連接,請使用自己的云主機ip(前置机器)進行轉發,轉發教程:端口轉發 其中 被轉發服務器相關信息填寫我們的入口信息即可 同時請發送工單(售後服務部門)提供你的固定ip,只有該IP可以連接. 請確保你的雲主機ip(前置机器)的 80 443 其中任一端口可被訪問 我們會驗證你的端口為可訪問狀態 你的固定ip才可以連接(只首次驗證). 建議將雲主機ip的ssh端口設置為80或者443 更改教程:更改SSH登陸端口
Showing the 12 most recent of 20 posts we hold for @hmbcloud_noc. 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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“🌜半月灣🌛 NOC 及其它” (@hmbcloud_noc), 313 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/hmbcloud_noc.
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.