我们预计将对 Lite 系列节点进行一次整体改造与优化。为了集中资源、改善稳定性与带宽利用率,本次调整将会 适当减少 Lite 节点数量。 改造期间,部分 Lite 节点可能会陆续下线、调整或暂时不可用。建议大家先使用目前已经上线的 直连节点 作为临时过渡。 本次改造预计将在 24 小时内完成。完成后我们会重新整理节点资源,并进一步优化整体连接质量。 对此期间可能带来的不便,我们深表歉意,感谢大家的理解与耐心等待。
👎11❤2🤡1😱1

Channel
@ssoneio
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
4,698subscribers
+55 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002165104487 |
|---|---|
| Type | Channel |
| Username | @ssoneio |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/ssoneio |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 20:07 | 4,698 | +8 |
| 27 Aug 2026, 23:04 | 4,690 | +10 |
| 24 Aug 2026, 18:45 | 4,680 | +3 |
| 20 Aug 2026, 19:52 | 4,677 | +5 |
| 18 Aug 2026, 00:07 | 4,672 | +9 |
| 14 Aug 2026, 13:45 | 4,663 | +7 |
| 10 Aug 2026, 21:57 | 4,656 | +12 |
| 8 Aug 2026, 08:14 | 4,644 | +1 |
| 7 Aug 2026, 14:47 | 4,643 | first reading |
23 posts held, back to 23 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 6 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 10 August 2026 |
|---|---|
| Posts held | 23 (23 June 2026 – 10 August 2026) |
| Views total | 3,979 |
| Reactions total | 50 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 05:39 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.
474 reactions across 23 posts, in 11 distinct kinds. The most used accounts for 43.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👎 | 208 | 43.9% | |
| 🤡 | 67 | 14.1% | |
| 👍 | 66 | 13.9% | |
| 💩 | 61 | 12.9% | |
| ❤ | 57 | 12.0% | |
| 🤣 | 8 | 1.69% | |
| 👏 | 2 | 0.422% | |
| 🤬 | 2 | 0.422% | |
| 🔥 | 1 | 0.211% | |
| 😱 | 1 | 0.211% | |
| 🤔 | 1 | 0.211% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 23 of the 23 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 474reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 23 most recent posts we hold, published 23 June 2026 to 10 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
我们预计将对 Lite 系列节点进行一次整体改造与优化。为了集中资源、改善稳定性与带宽利用率,本次调整将会 适当减少 Lite 节点数量。 改造期间,部分 Lite 节点可能会陆续下线、调整或暂时不可用。建议大家先使用目前已经上线的 直连节点 作为临时过渡。 本次改造预计将在 24 小时内完成。完成后我们会重新整理节点资源,并进一步优化整体连接质量。 对此期间可能带来的不便,我们深表歉意,感谢大家的理解与耐心等待。
👎11❤2🤡1😱1
经过紧急调整与优化,目前 Pro 套餐节点的速率已经得到明显改善,相比之前的异常状态已基本恢复可用。 不过需要说明的是,目前还不是我们最终计划的线路状态。现有可用带宽仍然存在一定压力,尤其在高峰时段,部分用户仍可能遇到速率波动。 我们会继续协调上游、增加带宽与优化负载,尽可能彻底解决目前的带宽不足问题。 感谢大家这段时间的耐心等待与理解。我们会继续处理,直到整体线路恢复到更理想的水平。
👎2❤1
目前 Pro 套餐线路速率出现明显下降。 经上游确认,由于光缆意外被挖断,导致线路容量受到影响,目前抢修工作正在进行中。 📌 当前情况 ⚠️ 主要影响 Pro 套餐用户 📉 可能出现速度下降、延迟升高等情况 👷 上游已组织人员进行紧急抢修 📌 临时建议 在抢修完成之前,建议大家可暂时使用直连 Mieru 节点作为过渡,应急使用。 待光缆修复完成后,线路将恢复正常
❤4🔥1
Lite 线路临时切换通知 尊敬的用户, 目前部分上游线路出现异常,导致 Lite 套餐部分节点的连接质量受到影响。为保障基础可用性,我们已将 Lite 流量临时切换至备用线路运行。 切换期间可能会出现: 速度下降 延迟升高 短时连接波动 我们已联系上游服务商进行处理,待故障修复后将恢复至正常线路。 请大家耐心等待,由此带来的不便我们深表歉意,感谢您的理解与支持!
👎21❤3🤬2🤔1
经过持续优化与调整,目前带宽问题已得到部分缓解,整体网络质量较之前已有明显改善。 ✅ 当前恢复情况 Lite 套餐节点已基本恢复正常使用 🚀 整体速度与稳定性均有所提升 🔁 此前频繁出现的长时间断流、掉线问题将得到大幅改善 📌 后续计划 我们仍将继续扩容带宽、优化线路,并持续观察网络运行情况,进一步提升整体稳定性和使用体验。 如果您仍遇到个别节点异常,可尝试更新订阅或切换其他节点,并及时向我们反馈,我们会持续跟进处理。 感谢大家这段时间的耐心等待与理解,我们也会继续努力,为大家提供更加稳定、流畅的服务体验!
👎18❤7
尊敬的用户, 我们深知目前 Lite 套餐用户 正面临带宽不足、速度波动和稳定性下降的问题,对此我们深表歉意。 目前我们已经制定了扩容计划,并将在月初增加更多带宽资源,从根本上解决目前带宽不足的问题。 📌 为什么还需要等待? 由于上游带宽资源均按整月采购,新的带宽资源需要等到后天才能正式交付并投入使用,因此目前我们无法立即完成扩容。 📅 预计恢复时间 ✅ 后天完成新增带宽交付 ✅ 月初完成扩容上线 ✅ 届时将明显改善 Lite 套餐的速度与稳定性 我们理解大家对网络质量的期待,也感谢大家这段时间的耐心与支持。请再给我们一点时间,我们会尽快完成扩容,恢复到应有的服务水平。 再次向大家表示诚挚的歉意,感谢大家一直以来的理解与支持!🙏
🤡15❤7👎4👏2
尊敬的用户, 我们计划于今晚更新一次节点配置,本次调整将影响所有 Lite的 VLESS 节点。 请使用 Lite VLESS 节点的用户在更新完成后,务必在客户端中更新一次订阅;如更新后仍然异常,建议删除旧配置并重新导入订阅。 目前存在的带宽不足问题,我们预计将在月初完成进一步扩容和处理。在彻底解决前,部分时段仍可能出现速度下降或线路波动。 对此给大家带来的不便,我们深表歉意,感谢大家的理解与耐心等待。
👎12🤡8❤1
近期如遇节点无法连接,请先更新订阅;若仍然异常,请删除旧配置后重新导入。 我们会根据线路运行情况不定期调整节点配置。客户端只有及时同步最新订阅,才能获得当前可用的节点参数;如果长期使用旧配置,可能出现节点超时、无法连接或节点缺失等情况。 ⚠️ 特别提醒 Lite 套餐客户 Lite 套餐节点的配置可能会随线路调整而更新。近期如果无法使用,请优先更新订阅;更新后仍无效时,请删除客户端中的旧配置,再重新导入订阅。 🚑 Mieru 直连节点 我们同时提供 Mieru 协议的直连节点 成功更新或重新导入订阅后,Mieru 节点通常位于节点列表最下方 Mieru 需要较新版本的客户端支持;如果看不到或无法使用,请先升级到最新版客户端,再次更新或重新导入订阅 ✅ 建议操作顺序 更新订阅 → 仍异常则删除旧配置并重新导入 → 看不到 Mieru 节点则升级客户端后再次同步。 请养成定期更新订阅的习惯,以便及时获取最新节点配置。感谢您的…
👎27❤4🤡2
简洁版网站目前正在维护中,暂时无法访问,稍后将恢复正常。 给您带来的不便,敬请谅解。
👎13💩8
📢 服务恢复进展通知 目前节点速率已在逐步恢复,我们对服务器节点参数进行了优化调整。**请所有用户更新订阅或重新导入节点**,以获取最新配置。 由于目前线路仍在持续调整中,短时间内可能还会存在一定波动。如果遇到节点无法使用,请按以下顺序尝试: 1. 更新订阅; 2. 重新导入节点; 3. 重启客户端; 4. 如仍无法解决,请卸载客户端后重新安装。 目前我们已经新增了一批**直连 Mieru 协议节点**,位于**节点列表最后**,大家可以优先使用作为临时方案。 如果更新订阅或重新导入后仍然没有看到 Mieru 节点,请升级客户端到最新版本。 其中 Shadowrocket(小火箭) 用户建议直接**卸载后重新安装最新版本**,否则可能无法获取新的协议节点。 非常抱歉给大家带来不便,我们仍在持续优化线路,感谢大家的理解与耐心支持。后续如有新的进展,我们会第一时间发布公告。
👎21❤6
近期由于线路持续出现波动,导致部分用户的使用体验受到影响。我们目前仍在全力协调上游、持续优化线路,争取尽快恢复到最佳状态。 我们深知这段时间给大家带来了诸多不便,对此深表歉意。 🎁 补偿方案 为了感谢大家的理解与支持,也为了弥补此次故障带来的影响,我们决定: ✅ 已为所有当前套餐未到期的用户,统一免费延长 一个月 使用时长。 📌 补偿对象: 所有当前套餐仍在有效期内的用户 无需申请,我们已自动发放 我们知道,任何补偿都无法完全弥补这段时间给大家带来的困扰,但这是我们的一点心意。 后续我们仍会继续优化线路、增加冗余资源,并尽快完成协议升级,努力让服务恢复到应有的稳定水平。 再次向大家表示诚挚的歉意,也感谢大家一直以来的理解、包容与支持。
👍43👎22💩9❤7
为了提升网络稳定性与后续维护能力,我们预计将在今晚开始进行协议升级。 📌 请所有用户务必注意 ✅ 请提前升级客户端至最新版本,以确保能够正常使用新的协议。 ⚠️ 如果继续使用旧版本客户端,可能会出现: 无法获取新节点 无法连接节点 订阅更新失败 新协议不兼容等问题 ⏳ 关于当前网络情况 我们也知道,近期网络确实非常不稳定。 由于当前整体网络环境变化较大,上游线路与入口资源频繁调整,我们一直在不断优化和尝试新的解决方案。本次协议升级也是为了进一步提升后续的稳定性、兼容性以及抗干扰能力。 对此给大家带来的影响,我们深感抱歉,也非常感谢大家一直以来的理解与耐心。 📌 建议所有用户今晚提前完成以下操作: 更新客户端至最新版本 更新订阅 如遇异常,建议删除旧配置后重新导入订阅 后续协议切换完成后,我们将第一时间发布恢复及更新公告。
👎13🤣8❤5
Showing the 12 most recent of 23 posts we hold for @ssoneio. 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“SSONE内卷报告” (@ssoneio), 4,698 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/ssoneio.
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.