Channel
@Mdsscloud
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,758subscribers
-46 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001453460449 |
|---|---|
| Type | Channel |
| Username | @Mdsscloud |
| Created | Between 1 April 2019 and 31 October 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 | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/Mdsscloud |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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, 02:55 | 1,758 | -2 |
| 10 Sept 2026, 22:20 | 1,760 | -6 |
| 5 Sept 2026, 13:59 | 1,766 | -4 |
| 1 Sept 2026, 10:16 | 1,770 | -5 |
| 29 Aug 2026, 03:25 | 1,775 | +1 |
| 25 Aug 2026, 18:33 | 1,774 | -5 |
| 22 Aug 2026, 22:53 | 1,779 | -6 |
| 19 Aug 2026, 09:34 | 1,785 | -4 |
| 16 Aug 2026, 05:54 | 1,789 | -5 |
| 12 Aug 2026, 20:37 | 1,794 | -4 |
| 9 Aug 2026, 22:12 | 1,798 | -5 |
| 6 Aug 2026, 17:00 | 1,803 | -1 |
| 6 Aug 2026, 09:02 | 1,804 | no change |
| 6 Aug 2026, 08:54 | 1,804 | first reading |
20 posts held, back to 10 May 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 4 August 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 8 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
🪧维护公告 为了保障线路稳定性过度节点已下线 通知频道已更换本频道将不再发送通知请您尽快关注最新MDSS官方通知频道 @mdss_announce - 香港02/香港04线路调整更换服务器且需要您更新订阅获取 - 优化TCP提高稳定性并有效的解决晚高峰断流问题 - 扩容现有内网带宽解决晚高峰拥护问题
Signed ONOKAZU
请大家快加新群哦~ @mdss_chat
请大家关注新的频道 @mdss_announce
运维已将美国01-04线路优化了AS46997线路，将采用用户端IPV4入口配合随机IPV6出口进行解锁Netflix/Disney+等流媒体，并尝试使用IPV6随机出口访问Google服务等。 🔨 解决流媒体解锁地区性问题，如果您不大幅度长时间多次快进跳着看的话，不会提示弹窗或者无法播放。 🔨 尝试解决IPV4地址被google标记送中问题，是否解决还有待测试。
公告： 线路已维修完毕 DNS解析已更新新机房 线路速率已恢复 如果着急的话 可以手动更新下订阅地址获取新节点 如果不急的话 可以等本地DNS生效 备注： 正在修复原节点，过度节点在维修完毕后，将在一个月内停止支持。请尽快更新订阅地址使用前排节点，最近线路波动大给您带来的不变，我们深感歉意。 目前线路已恢复如初。 原域名如果有被墙情况或者订阅被墙无法更新请用新域名登录 新域名 user.51mdss.com
深圳机房波动了一下，已经排除故障。
很抱歉的告诉各位，由于昨天晚上看直播的人太多，导致我们的宽带被挤爆了，好了现在人也到台湾了，是不是该消停一下了。
日本方向疑似CDN77出现故障，正在进一步排查中，loading.....
由于zenlayer香港出口国际方向播错路由了,很抱歉导致这么长时间中断，目前已经处理。
由于深圳移动运营商配错了路由，导致全国丢包，目前已经修复，请大家理性对待任何一个云厂商的出现的故障，主要还是看对故障的解决速度以及态度，谢谢各位老板，我们可以在任何时间，任何地点为客户处理故障，周末快乐。
观测到部分用户地区本地dns污染 间接性解析不了节点域名，导致所有节点超时，系统DNS更换为119.29.29.29 ，223.5.5.5 223.6.6.6 均可以解决。 提示：系运营商干的，不要怪机场，谢谢，如果您不懂如何更换默认DNS，可以联系我们网页右下角的客服给您处理。
Showing the 12 most recent of 20 posts we hold for @Mdsscloud. 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.
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“./Data/Mdss/Log” (@Mdsscloud), 1,758 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/Mdsscloud.
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.