如使用ClashMi最新版客户端 可按需关闭该选项 此选项为默认开启状态 https://t.me/zhetengsha/6619

Channel
公告板
@ssrdata
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
5,073subscribers
+1,328 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1003882217222 |
|---|---|
| Type | Channel |
| Username | @ssrdata |
| Created | 12 February 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/ssrdata |
Topic
Technology — 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 13 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 12:06 | 5,073 | +66 |
| 31 Oct 2026, 02:08 | 5,007 | +66 |
| 28 Oct 2026, 03:25 | 4,941 | +59 |
| 25 Oct 2026, 02:56 | 4,882 | +26 |
| 22 Oct 2026, 06:21 | 4,856 | +45 |
| 18 Oct 2026, 23:11 | 4,811 | +35 |
| 15 Oct 2026, 23:07 | 4,776 | +45 |
| 12 Oct 2026, 14:39 | 4,731 | +104 |
| 5 Oct 2026, 13:20 | 4,627 | +117 |
| 28 Sept 2026, 02:19 | 4,510 | +299 |
| 18 Sept 2026, 06:54 | 4,211 | +47 |
| 13 Sept 2026, 19:58 | 4,164 | +43 |
| 10 Sept 2026, 10:37 | 4,121 | +62 |
| 4 Sept 2026, 22:18 | 4,059 | +35 |
| 1 Sept 2026, 12:47 | 4,024 | +40 |
| 29 Aug 2026, 16:44 | 3,984 | +29 |
| 26 Aug 2026, 21:57 | 3,955 | +34 |
| 24 Aug 2026, 05:19 | 3,921 | +55 |
| 20 Aug 2026, 02:33 | 3,866 | +21 |
| 16 Aug 2026, 21:36 | 3,845 | first reading |
Engagement
12 posts held, back to 12 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. 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 12 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
已将电源漏电防火墙下架。目前全部香港可正常连接。
部分香港接入所在机柜由于未知原因短路导致机柜柜体带电。目前已将机柜电源整体断开检查漏电问题。部分接入可能暂时无法链接。香港高松灯接入不受影响。
更新订阅并不需要登陆官网进行任何操作。于客户端内点击订阅更新按钮即可。 Clash Verge客户端左侧选择订阅 于右上角点击 更新所有订阅 即可正常连接使用。
我们已完成全部底层握手域名更换。 订阅配置需更新到最新版本后可正常连接。
由于底层握手域名更换,之前订阅的配置文件将无法使用。 我们建议开启客户端内的自动订阅更新设置,设置频率为每日更新。更换将由香港/台湾开始。 目前我们已完成高松灯/精品BGP系列接入更换。 位于现有配置线路列表第一条的 “官网” 此次不会更换底层配置。如有需要可连接该线路进行更新订阅配置文件。
由于我们的通用配置 www.microsoft.com 于近日对我们的请求开始限速,导致urltest测速可能会随机出现timeout。 该问题不影响实际连接时的数据握手。 我们目前已经开始对使用域名进行更换。
我们已完成处理连接随机断开的问题。 我们使用Cloudflare CDN于服务端全球数据同步。但数日前Cloudflare于没有任何通知的情况下为我们的服务自动添加速率限制,导致后端同步用户信息过程中会随机丢弃部分用户的同步使用信息。该部分被随机丢弃的用户会短暂被线路断开连接。但此部分信息可能在下一次数据同步中被传输至服务端遂可正常连接。 由于该限制为持续性限制,导致连接线路时表现为 可连接一段时间 后不可连接 后恢复正常连接。 我们目前已关闭Cloudflare自动添加的速率限制。目前已不会出现连接随机断开的情况。 我们对近日出现该随机断开连接的情况深表歉意。
当使用Clash Verge客户端并使用TUN模式时,请务必于Clash客户端左侧设置内 打开 DNS复写 选项。 如未开启该选项,由于DNS查询机制问题,包括但不限于会造成: 线路测试连接时大规模测速失败 或 Youtube等网页可能出现需要花费数十秒后加载 或 网页完全无法加载 或 Youtube连接只有几百KB 等各类使用问题。 当发现Telegram连接正常但网页或APP无法正常加载或使用时,请务必检查是否 打开DNS复写。 以及我们建议于设置内打开统一延迟开关。
由于我们的电信回程路由于部分地区被整段ip空路由,以及某些路由正常的城域网下整段ip被限速1Mbps,导致部分地区于电信运营商下连接速度出现严重问题。 作为临时性缓解措施,现调整香港精品BGP全系列接入为1倍流量计费。如电信运营商下连接出现问题可连接香港精品系列接入。
我们认为未来有必要提供专属本站纯非标准协议连接客户端,该专属客户端将仅支持使用这里的服务使用。 考虑到完全封端将造成大量特殊设备无法使用并造成各类使用场景受限,我们会继续提供标准协议订阅使用。 专属客户端和标准协议基础订阅将完全独立供应,出现故障时,将尽可能减少同时受影响的使用场景。
Channel created
Showing the 12 most recent of 12 posts we hold for @ssrdata. 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.
Mentions
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.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“公告板” (@ssrdata), 5,073 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/ssrdata.
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.