着急的请到控制面板手动开机
👍5😭3

Channel
@NoSLA_Log
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
1,698subscribers
+720 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003946313931 |
|---|---|
| Type | Channel |
| Username | @NoSLA_Log |
| Created | Between 1 April 2026 and 12 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/NoSLA_Log |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 03:38 | 1,698 | +46 |
| 11 Nov 2026, 02:12 | 1,652 | +25 |
| 7 Nov 2026, 06:58 | 1,627 | +12 |
| 4 Nov 2026, 08:06 | 1,615 | +34 |
| 1 Nov 2026, 05:37 | 1,581 | +52 |
| 29 Oct 2026, 09:18 | 1,529 | +34 |
| 26 Oct 2026, 11:58 | 1,495 | +18 |
| 23 Oct 2026, 17:06 | 1,477 | +18 |
| 20 Oct 2026, 07:21 | 1,459 | +42 |
| 17 Oct 2026, 16:45 | 1,417 | +50 |
| 14 Oct 2026, 12:59 | 1,367 | +32 |
| 11 Oct 2026, 07:55 | 1,335 | +51 |
| 4 Oct 2026, 23:39 | 1,284 | +96 |
| 25 Sept 2026, 12:21 | 1,188 | +18 |
| 16 Sept 2026, 15:18 | 1,170 | +10 |
| 13 Sept 2026, 04:57 | 1,160 | +15 |
| 9 Sept 2026, 11:18 | 1,145 | +32 |
| 4 Sept 2026, 09:17 | 1,113 | +14 |
| 1 Sept 2026, 08:17 | 1,099 | +9 |
| 29 Aug 2026, 06:54 | 1,090 | first reading |
18 posts held, back to 12 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 1 page 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 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
282 reactions across 14 posts, in 10 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 😭 | 125 | 44.3% | |
| 👍 | 83 | 29.4% | |
| 🙏 | 30 | 10.6% | |
| 👏 | 14 | 4.96% | |
| 💯 | 9 | 3.19% | |
| ❤ | 8 | 2.84% | |
| 🎉 | 4 | 1.42% | |
| 😍 | 4 | 1.42% | |
| 🥰 | 3 | 1.06% | |
| 🔥 | 2 | 0.709% |
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 14 of the 18 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 282 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 12 June 2026 to 7 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.
着急的请到控制面板手动开机
👍5😭3
鉴于最近两次漏洞都是嵌套虚拟化产生的 未来任何宿主机都将禁用嵌套虚拟化
😭19👍5🎉3❤1
由于最新的高危漏洞,我将从现在起对所有宿主机进行升级和重启 此次行为不会发放补偿天数
😭33🥰1🙏1
新换了页面主题,如果您发现有bug,请截图并提交工单,谢谢!
💯9
📢 自助退款功能上线公告 即日起,您可在客户中心自助申请退款,无需提交工单。 ━━━━━━━━━━━━━━━━━━ 📍 使用方法 ━━━━━━━━━━━━━━━━━━ 客户中心 → 服务 → 选择对应服务 → Information 页面 → 点击「申请退款」按钮 → 选择语言 → 系统自动检测 → 查看方案 → 确认 ━━━━━━━━━━━━━━━━━━ 🔍 系统会自动检测两项 ━━━━━━━━━━━━━━━━━━ 1️⃣ 流量使用情况(当月已用流量) 2️⃣ 您服务器 IP 对中国大陆的连通性 ⚠️ 若您的服务器 IP 在中国大陆无法 ping 通, 将无法办理任何形式的退款,恕不例外。 ━━━━━━━━━━━━━━━━━━ 💰 退款方式一:原路退款(全额) ━━━━━━━━━━━━━━━━━━ 需 同时 满足以下条件: ✅ 服务开通未超过 24 小时(或特定标注) ✅ 当月双向流量使用低于 5 GB(或特定标…
❤7😭7🔥1
IP过白进度汇总: 🇩🇪德国法兰克福精品线路的新IP过白已经全部完成 但是目前不会更换 我会在宿主机发到德国之后进行更换(新宿主机CPU为EPYC 7663) 🇺🇸美国圣何塞精品线路的新IP过白已完成CN2/CUII,CMIN2还在委托上游催促 当我观察到CMIN2就绪之后,我会提前三天进行更换IP公告 🇭🇰香港普通线路的联通过白还在进行中,无具体ETA
👍19
#紧急通知 由于某IDC数据库泄露导致部分使用相同密码的用户账号被异常登录,为了保障您的财产安全,请您检查自己的账户情况及时修改密码
🙏10
已精准定位,你👌没了
👍49😭11👏9😍3🥰2
诚招全栈大佬 内容:写一个财务系统(全API,高扩展性,干净的数据库设计) 酬劳:面议 需具备技能: 具备独立处理前后端的能力 熟悉Laravel(12)框架 前端为Blade + Alpine.js + Tailwind 队列为database 驱动(检测到 Redis 时自动切换) 可从Blesta完全迁移 如您能胜任,请您写信至 [email protected]
🙏12👍1
当前香港标准优化由于上游问题存在一定的线路降级(回程当前为CMI) 此问题发生时间为7月25日,恢复时间未知 恢复后,我将为所有香港标准优化用户发放对等的补偿时间
😭16🙏4👍2🎉1
警告: 近期经用户反馈IPv6至大陆路由存在无法连通现象,请自行检测本机IPv6与全球互联状态 如需更换IPv6 费用为 15CNY/次
😭6
🇩🇪德国法兰克福标准优化线路开启预购🇩🇪 CT去程直连,CU去程9929,CM去程CMIN2 CT回程9929,CU回程9929,CM回程CMIN2 👌批量采购宿主机(AMD EPYC) + 高带宽 + 高冗余 🤩欧洲方向性价比最优解! ———————————————————————— 法兰克福-标准优化-预购款-S 先测个速 立即下单 1C / 1G / 15G / 1000G @ 500Mbps 329CNY/年 ! 法兰克福-标准优化-预购款-M 先测个速 立即下单 2C / 2G / 30G / 2000G @ 700Mbps 599CNY/年 ! 法兰克福-标准优化-预购款-L 先测个速 立即下单 4C / 4G / 60G / 4000G @ 1Gbps 959CNY/年 ! —————————————————————…
😭5🙏3👍2😍1
Showing the 12 most recent of 18 posts we hold for @NoSLA_Log. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“NoSLA工作日志” (@NoSLA_Log), 1,698 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/NoSLA_Log.
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.