🟢 HKG EB IP Transit 线路维护 轻微故障 · 已完成 · 2026-11-01 06:37 UTC 已完成 2026-11-01 06:37 UTC 维护已完成。 进行中 2026-10-31 00:00 UTC 维护已开始。 已计划 2026-10-31 00:00 UTC 受 IP Transit 线路维护影响,HKG EB 当前服务性能下降。 预计恢复时间:2026年11月3日
Signed DMIT NOC

Channel
@DMIT_INC_CN
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
11,104subscribers
+772 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001343393147 |
|---|---|
| Type | Channel |
| Username | @DMIT_INC_CN |
| Description | DMIT 公告与服务状态推送 📢 https://dmit.news # 信息 📊 https://does.dmit.fail # 状态 |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 62 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/DMIT_INC_CN |
Hacking & security — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 87% 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 |
|---|---|---|
| 6 Nov 2026, 11:08 | 11,104 | +13 |
| 5 Nov 2026, 11:27 | 11,091 | +7 |
| 4 Nov 2026, 10:45 | 11,084 | +12 |
| 3 Nov 2026, 12:29 | 11,072 | +22 |
| 2 Nov 2026, 08:46 | 11,050 | +8 |
| 1 Nov 2026, 10:15 | 11,042 | +8 |
| 31 Oct 2026, 11:10 | 11,034 | +12 |
| 30 Oct 2026, 11:37 | 11,022 | +10 |
| 29 Oct 2026, 14:47 | 11,012 | +6 |
| 28 Oct 2026, 17:29 | 11,006 | +31 |
| 27 Oct 2026, 17:41 | 10,975 | +21 |
| 26 Oct 2026, 14:39 | 10,954 | +12 |
| 25 Oct 2026, 14:35 | 10,942 | +10 |
| 24 Oct 2026, 11:36 | 10,932 | +7 |
| 23 Oct 2026, 12:35 | 10,925 | +18 |
| 22 Oct 2026, 14:56 | 10,907 | +2 |
| 21 Oct 2026, 11:56 | 10,905 | +17 |
| 20 Oct 2026, 07:39 | 10,888 | +9 |
| 19 Oct 2026, 04:27 | 10,879 | +1 |
| 18 Oct 2026, 04:57 | 10,878 | first reading |
35 posts held, back to 15 June 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 47 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 1 November 2026 |
|---|---|
| Posts held | 35 (15 June 2026 – 1 November 2026) |
| Views total | 84,410 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 20:24 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Telegram’s own ‘edited’ marker: 5 of 6 posts held from the last 30 days (83.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🟢 HKG EB IP Transit 线路维护 轻微故障 · 已完成 · 2026-11-01 06:37 UTC 已完成 2026-11-01 06:37 UTC 维护已完成。 进行中 2026-10-31 00:00 UTC 维护已开始。 已计划 2026-10-31 00:00 UTC 受 IP Transit 线路维护影响,HKG EB 当前服务性能下降。 预计恢复时间:2026年11月3日
Signed DMIT NOC
🟢 DMIT 客服等待时间增加 提示信息 · 已恢复 · 2026-11-05 10:27 UTC 已恢复 2026-11-05 10:27 UTC 客户支持服务已恢复正常运行状态。 已迁移 2026-10-27 04:22 UTC DMIT 客户支持当前负载较高。 我们建议您优先使用自助服务功能,以减少等待时间。
Signed DMIT NOC
🟢 LAX AS9929 骨干网丢包升高 轻微故障 · 已恢复 · 2026-10-22 07:30 UTC 已恢复 2026-10-22 07:30 UTC 中国联通已确认该问题已解决。 观察中 2026-10-21 03:25 UTC DMIT 尚未收到来自中国联通的任何更新。 但我们观察到丢包现象在发生后 6 小时内停止。 排查中 2026-10-20 06:38 UTC DMIT 监测到 LAX 区域的 AS9929 骨干网目前存在较高的丢包。我们已就此问题向运营商联系,并正在敦促其进行排查。我们将随时同步后续进展。感谢您的理解与耐心。
Signed DMIT NOC
🟢 计划维护:为CVE-2026-99999部署在线内核补丁 轻微故障 · 已完成 · 2026-10-21 03:31 UTC 已完成 2026-10-21 03:31 UTC 所有节点均已针对 CVE-2026-99999 完成热补丁。 进行中 2026-10-19 08:00 UTC 维护已开始。 已计划 2026-10-19 08:00 UTC DMIT 将在 2026 年 10 月 19 日至 10 月 23 日期间,为所有区域的所有宿主机部署自行编译的在线内核补丁,以缓解 CVE-2026-99999。 除东京区域外,预计不会出现停机。 如果需要重启,虚拟机可能会经历长达 120 分钟的停机。
Signed DMIT NOC
🟢 东京区域软件和内核计划升级 轻微故障 · 已完成 · 2026-10-21 03:26 UTC 已完成 2026-10-21 03:26 UTC 东京所有节点已经完成内核与软件更新。 进行中 2026-10-19 08:00 UTC 维护已开始。 已计划 2026-10-19 08:00 UTC 东京区域的软件和内核版本低于其他区域。 软件和内核升级已列入计划。 每次虚拟机停机时间最长 120 分钟。
Signed DMIT NOC
2026年10月15日起,通过社交账号注册的客户需要设置登录密码。 影响提醒 · 2026-10-14 23:34 UTC 自 2026 年 10 月 15 日起,通过社交账号注册且从未设置过密码的客户,需要设置一个登录密码。您登录客户区域后会收到提示,请在宽限期内完成设置,以免影响客户区域功能。 全文见状态页。
Signed DMIT NOC
Channel name was changed to «LANG=zh_CN tail -f /var/log/DMIT.log»
转换为自主管理 IP 地址 影响提醒 · 2026-09-29 04:48 UTC 更新:Cogent IP 自助切换已开放及计费说明 全文见状态页。
Signed DMIT NOC
🟢 CoreSite LA2 的 CN2 GIA 接入点性能下降 轻微故障 · 已恢复 · 2026-09-18 16:36 UTC 中国电信表示,他们在CoreSite LA位置遇到的问题已解决。DMIT已重新加载了从中国电信CoreSite LA接收到的路由。
Signed DMIT NOC
🟢 CoreSite LA2 的 CN2 GIA 接入点性能下降 轻微故障 · 已恢复 · 2026-09-18 16:36 UTC 已恢复 2026-09-18 16:36 UTC 中国电信表示,他们在CoreSite LA位置遇到的问题已解决。DMIT已重新加载了从中国电信CoreSite LA接收到的路由。 观察中 2026-09-18 09:05 UTC DMIT 监测到位于 CoreSite LA2 的 CN2 GIA 接入点出现丢包。我们已将流量切换至 DRT CN2 GIA 接入点。目前所有产品的网络性能未受影响。
Signed DMIT NOC
DMIT 新状态页上线了 消息 · 2026-09-10 18:49 UTC DMIT 的新状态页今天上线,地址是 [does.dmit.fail](https://does.dmit.fail)。 全文见状态页。
Signed DMIT NOC
目前已对所有未完成整改的服务执行服务暂停,并向受影响的客户创建了工单。接下来受影响的客户可以通过工单与我们的工作人员联系解除服务的暂停并尽快修复安全问题。 修改程序/修复漏洞后可以通过下面的测试工具检查问题是否已经修复。 https://dmit-abuse-team-temp-security-response.dmit.com/
Signed Still
Showing the 12 most recent of 35 posts we hold for @DMIT_INC_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.
@DMIT_INC_CN edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“LANG=zh_CN tail -f /var/log/DMIT.log” (@DMIT_INC_CN), 11,104 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/DMIT_INC_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.