目前已对所有未完成整改的服务执行服务暂停,并向受影响的客户创建了工单。接下来受影响的客户可以通过工单与我们的工作人员联系解除服务的暂停并尽快修复安全问题。 修改程序/修复漏洞后可以通过下面的测试工具检查问题是否已经修复。 https://dmit-abuse-team-temp-security-response.dmit.com/
Signed Still

Channel
@DMIT_INC_CN
On this record: Topic · Growth · Engagement · Posts · Citations · Telegram's recommendations · Cite this entry
10,783subscribers
+451 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 |
| 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 | 19 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 19 September 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 10:17 | 10,783 | +23 |
| 17 Sept 2026, 00:41 | 10,760 | +11 |
| 15 Sept 2026, 04:58 | 10,749 | +10 |
| 13 Sept 2026, 15:55 | 10,739 | +19 |
| 11 Sept 2026, 20:40 | 10,720 | +43 |
| 9 Sept 2026, 09:19 | 10,677 | +16 |
| 6 Sept 2026, 01:59 | 10,661 | +17 |
| 3 Sept 2026, 18:39 | 10,644 | +16 |
| 2 Sept 2026, 07:24 | 10,628 | +11 |
| 1 Sept 2026, 07:39 | 10,617 | +17 |
| 31 Aug 2026, 06:28 | 10,600 | +10 |
| 30 Aug 2026, 09:45 | 10,590 | +20 |
| 29 Aug 2026, 11:08 | 10,570 | +59 |
| 28 Aug 2026, 10:58 | 10,511 | +29 |
| 27 Aug 2026, 08:37 | 10,482 | +10 |
| 26 Aug 2026, 05:48 | 10,472 | +1 |
| 25 Aug 2026, 02:45 | 10,471 | +5 |
| 23 Aug 2026, 19:36 | 10,466 | +15 |
| 22 Aug 2026, 01:43 | 10,451 | +17 |
| 20 Aug 2026, 17:46 | 10,434 | first reading |
24 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 39 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 31 August 2026 |
|---|---|
| Posts held | 24 (15 June 2026 – 31 August 2026) |
| Views total | 32,620 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 1 Sept 2026, 20:41 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.
目前已对所有未完成整改的服务执行服务暂停,并向受影响的客户创建了工单。接下来受影响的客户可以通过工单与我们的工作人员联系解除服务的暂停并尽快修复安全问题。 修改程序/修复漏洞后可以通过下面的测试工具检查问题是否已经修复。 https://dmit-abuse-team-temp-security-response.dmit.com/
Signed Still
https://telegra.ph/DMIT-2026%E5%B9%B48%E6%9C%8826%E6%97%A5%E7%BD%91%E7%BB%9C%E5%AE%89%E5%85%A8%E9%80%9A%E6%8A%A5-08-29 DMIT 服务自测工具 https://dmit-abuse-team-temp-security-response.dmit.com/
Signed Still
第二次安全检查已经完成 开机后未修改程序/修复漏洞的VM已再次被关机 第三次将执行服务暂停与 Abuse 罚款
Signed Austin C.
DMIT 已在北京时间 8月28日凌晨3时许对受影响的VM执行了关机操作,并向受影响的客户发送了通知邮件,请所有受影响的客户在收到邮件后检查并完成相关修复工作。 *您的VM并未暂停,DMIT 目前仅执行了关机操作,您可以随时开机并恢复您的使用。 确认整改完成后,您无需提交工单,IP 更改限制将在72个小时内自动解除,DMIT 会在接下来的工作中持续观察问题是否仍然存在,若问题仍然存在,DMIT 将会建议客户再次检查(您将再次收到新的邮件)。 另,由于目前工单系统压力激增,您的请求可能有所延迟。
Signed Still
DMIT proactive security detected that 2% of tenants were deploying potentially risky applications in the DMIT LAX data center. These tenants' applications sent significant large traffic to China several hours ago. - DMIT detected abnormal traffic within the network 12 hours ago but took no action due to complexity. - However, this potential risk factor was officially exploited 8 hours ago. - DMIT will officially not…
Signed Still
DMIT Inc - NOC工作日志 pinned «尊敬的客户,您好: 在过去这一两年中,全球 IP 地址的租赁成本一直在持续上涨。由于租赁 IP 受市场波动、供应商政策调整以及合同期限等诸多因素影响,在长期稳定性和自主掌控力方面确实存在一定的局限。为了给您提供更长期、稳定且可靠的服务环境,同时也为了尽最大努力减轻成本上涨对您带来的影响,DMIT 近期已全面转向自购并独立管理 IP 地址的模式。我们希望通过这一举措,最大程度地自行消化成本压力,避免将这部分费用转嫁给您。 不过,我们也充分考虑到部分客户可能因业务需要,仍有保留现有 Cogent IP 地址(即…»
尊敬的客户,您好: 在过去这一两年中,全球 IP 地址的租赁成本一直在持续上涨。由于租赁 IP 受市场波动、供应商政策调整以及合同期限等诸多因素影响,在长期稳定性和自主掌控力方面确实存在一定的局限。为了给您提供更长期、稳定且可靠的服务环境,同时也为了尽最大努力减轻成本上涨对您带来的影响,DMIT 近期已全面转向自购并独立管理 IP 地址的模式。我们希望通过这一举措,最大程度地自行消化成本压力,避免将这部分费用转嫁给您。 不过,我们也充分考虑到部分客户可能因业务需要,仍有保留现有 Cogent IP 地址(即 154 开头 IP)的需求。为了尽量满足大家的个性化业务场景,我们决定继续保留这部分 IP 的使用选项。但由于该类 IP 的外部租赁成本持续增加,自 2026 年 12 月 1 日起,我们将不得不针对继续保留 154 开头 IP 的产品收取额外的租金补贴费用,标准为每月 1 USD/IPv4。此项费用将自动附加在您的相关…
Signed Still
DMIT 现在支持使用 Passkey 进行快捷登录和两步验证。 有需要的客户可以点击以下链接前往设定和开启。 https://www.dmit.io/clientarea.php?action=security *若开启了两步验证,请务必保存好您的备份码,以免遗失后无法正常登入账户。
Signed Still
🧭 新增可用区: 计划于 2025 年底前在洛杉矶新增一个 独立可用区。 因电力不足且无法继续扩容,又因价格上涨至与高品质数据中心无异。无继续留存必要性。
Signed Austin C.
维护通知 区域:洛杉矶数据中心 范围:AN4/AN5虚拟化节点 影响:约为5分钟,不超过30分钟,每次操作一个节点 日期:2026-07-16 至 2026-07-31 UTC 原因:新数据中心设施交付完毕,现有数据中心电力构架存在缺陷,到期迁移所有现有基础设施至更高标准数据中心。
Signed Austin C.
DMIT Inc - NOC工作日志 pinned «https://telegra.ph/DMIT-ToS-Change-Summary-07-16»
https://telegra.ph/DMIT-ToS-Change-Summary-07-16
Signed Still
Showing the 12 most recent of 24 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“DMIT Inc - NOC工作日志” (@DMIT_INC_CN), 10,783 subscribers as measured 19 September 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.