Channel
@DMIT_INC_CN
On this record: Growth · Engagement · Posts · Citations · Cite this entry
10,399subscribers
+67 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 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/DMIT_INC_CN |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 20:58 | 10,399 | +16 |
| 13 Aug 2026, 11:15 | 10,383 | +1 |
| 12 Aug 2026, 13:27 | 10,382 | -1 |
| 11 Aug 2026, 16:27 | 10,383 | +6 |
| 10 Aug 2026, 17:04 | 10,377 | +14 |
| 9 Aug 2026, 15:15 | 10,363 | +5 |
| 8 Aug 2026, 15:41 | 10,358 | +10 |
| 7 Aug 2026, 18:31 | 10,348 | +1 |
| 6 Aug 2026, 21:28 | 10,347 | +15 |
| 6 Aug 2026, 04:15 | 10,332 | no change |
| 6 Aug 2026, 04:08 | 10,332 | first reading |
19 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 16 pagesof 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 29 July 2026 |
|---|---|
| Posts held | 19 (15 June 2026 – 29 July 2026) |
| Views total | 64,590 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 05:13 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.
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
所有订单正在逐步开通，当您的服务置于审核中（Pending）时，请不要担心，您的服务将按照订单顺序自动开通，此过程中无需人工审核，当您的订单激活时，您会收到邮件通知。
Signed Still
订单将按照自动化任务排队开通，这可能需要一些时间，在开通之前，您的服务将保持为 Pending 状态。 由于目前工单数量激增，退款处理可能会有所减慢，如果您需要退款，为了减少您的等待时间，您可以使用自助退款渠道来请求退款。 在产品控制面板的计费选项卡中可以找到退款按钮并按照适用的规则发起退款请求。
Signed Still
在更改IP地址时，请确保您的VM已经正确运行和配置Cloud-init组件，这在 DMIT 提供的系统模版中默认运行并且无需人工干预，如果您通过其他方式移除了此组件或者安装了非 DMIT 提供的系统模版，您可能需要手动来完成IP地址的配置。
Signed Still
免费无条件自助更改 IPv4 地址的机会已经发放，免费机会可以在2026年9月1日之前使用，适用于所有在2026年7月1日之前创建的产品服务，每个服务限用一次，无额外限制条件且无需人工审核。 请注意，IP地址一旦更改无法撤回，且 DMIT 不保证 IP 地址在任何第三方网站、流媒体平台、以及 AI 服务的可访问性，也不保证 IP 地址在特定测试平台的地理位置信息。 *在更改IP地址时，请确保您的VM已经正确运行和配置Cloud-init组件，这在 DMIT 提供的系统模版中默认运行并且无需人工干预，如果您通过其他方式移除了此组件或者安装了非 DMIT 提供的系统模版，您可能需要手动来完成IP地址的配置。
Signed Still
安全维护通知 区域：洛杉矶与香港数据中心 范围：部分 KVM 虚拟化节点 影响：部分客户 VM 可能经历短暂重启或临时服务中断 日期：2026-07-07 UTC 原因：针对 Januscape（CVE-2026-53359）进行缓解处理 DMIT 已重启部分服务及相关虚拟化组件，以缓解近期披露的 Januscape 安全漏洞。 Januscape 影响 KVM/x86 虚拟化隔离。为降低潜在风险并维护平台安全，我们已对 LAX 与 HKG 受影响的服务组件执行受控重启。本次操作按批次进行，以尽量减少同时受影响的客户范围。 当前状态： 必要的服务重启已完成。 受影响服务仍在持续监控中。 后续如需更新内核或虚拟化组件，可能仍会安排维护窗口。 除非另行通知，客户目前无需执行额外操作。 对此次短暂服务中断可能造成的不便，我们深表歉意。 DMIT 将继续关注相关情况，并在必要时执行进一步更新。
Signed Still
Showing the 12 most recent of 19 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.
Citation-graph rank — 71,013 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“DMIT Inc - NOC工作日志” (@DMIT_INC_CN), 10,399 subscribers as measured 14 August 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.