Channel
@bagenotice
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,350subscribers
-68 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002142733828 |
|---|---|
| Type | Channel |
| Username | @bagenotice |
| Created | Between 1 November 2023 and 31 May 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/bagenotice |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 02:24 | 4,350 | -8 |
| 26 Aug 2026, 22:48 | 4,358 | -11 |
| 24 Aug 2026, 08:07 | 4,369 | -6 |
| 20 Aug 2026, 19:08 | 4,375 | -4 |
| 18 Aug 2026, 00:51 | 4,379 | -9 |
| 15 Aug 2026, 01:45 | 4,388 | -16 |
| 11 Aug 2026, 08:05 | 4,404 | -15 |
| 8 Aug 2026, 06:27 | 4,419 | +1 |
| 7 Aug 2026, 16:46 | 4,418 | first reading |
20 posts held, back to 31 January 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 5 pagesof 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 15 July 2026. An engagement rate over an empty window would be a number about nothing.
123 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 43.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 53 | 43.1% | |
| ❤ | 42 | 34.1% | |
| 💩 | 20 | 16.3% | |
| 👏 | 4 | 3.25% | |
| 👌 | 1 | 0.813% | |
| 👎 | 1 | 0.813% | |
| 🤮 | 1 | 0.813% | |
| 🥰 | 1 | 0.813% |
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 17 of the 20 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 123reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 31 January 2026 to 15 July 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.
#维护通知 Hong Kong 地区核心交换机维护通知/ Notice Regarding Core Switch Maintenance in the Hong Kong Region 尊敬的用户， 为了进一步提升网络服务质量与稳定性，我们计划对部分网络设备进行停机维护操作,届时，上述受影响线路将会出现短暂的网络中断。请您提前做好相关业务规划与数据保存，避免在维护时段内进行重要操作。网络将在维护结束后自动恢复正常。 具体维护安排如下： 开始时间：2026年07月22日 00:00 结束时间：2026年07月22日 01:00 受影响范围: Hong Kong区域所有实例 维护内容: 更新核心交换机固件，来进行修复旧内核引发ipv6 ra的问题。 维护期间，相关业务可能出现网络中断情况。正常情况下仅会产生极短时间中断，极端情况下预计中断时间不超过 5 分钟。 请您提前做好相关业务安排。维护完成后，业务将自动恢复，无需额…
👍3👌1
尊敬的 BAGE 用户：Product Push 功能现已修复并重新开放 您好！ 我们很高兴地通知您，Product Push（产品所有权转移）功能已完成修复并通过稳定性验证，现正式重新开放使用。 费用: $1/次 在此期间给您带来的不便，我们深表歉意，并感谢您在维护期间的耐心与理解。 如果您在使用过程中遇到任何问题，欢迎随时通过工单或客服联系我们，我们将第一时间协助处理。 Dear BAGE User: The Product Push feature has been fixed and is now back online. Hello! We are pleased to inform you that the Product Push (product ownership transfer) feature has been repaired and verified for stability; it is now…
#异常通知 目前我们的网络正遭受大规模 UDP 拒绝服务（DDoS）攻击，导致部分地区的服务可用性受到影响。我们的网络团队已第一时间介入，目前正全力进行流量清洗与修复，我们将尽快恢复服务正常运行。 感谢您的理解与耐心体谅。 #Abnormal Notification Our network is currently experiencing a large-scale UDP DDoS attack, resulting in temporary service degradation in certain regions. Our network engineering team has responded immediately and is actively mitigating the traffic. We are working to restore full service operational status…
#异常通知 我们监控到 Germany 区域的1台节点 DEB 出现 硬件故障，上游正在安排远程手进行查看，请大家耐心等待。 给您带来不便深表歉意，如有其他疑问请提交服务单联系我们。 #Notification of Anomaly We have detected a hardware failure on one node DEB in the Germany region. Upstream personnel are arranging for remote assistance. Please wait patiently. We sincerely apologize for any inconvenience this may cause. For any further questions, please submit a service request to contact us.
目前已全部更新完成，感谢您的耐心等候和理解支持。 The update is now complete. Thank you for your patience, understanding and support.
#维护通知 日本Japan Standard区域维护通知 / Japan Standard Regional Maintenance Notice 尊敬的用户， 为了提供更加稳定与高效的网络服务，我们计划对Japan Standard地区节点的 宿主机内核进行更新，提升整体性能与稳定性。具体维护安排如下： 维护时间: 1，2026年5月20日 10:00 - 22:00 （UTC+8） 受影响范围: Japan Standard区域所有实例 维护内容: 更新宿主机内核到最新版本，来进行修复旧内核引发nvme掉速的问题。 在更新内核之后您的实例将会被重启，预计每台实例影响10-15分钟。 维护完成后，所有服务将自动恢复正常。 如有任何问题或需进一步了解相关信息，请随时联系技术支持团队。 感谢您的理解与支持！ Dear Users, To provide a more stable and efficient network…
❤2👍1
#英国地区 IP 更换公告 您好！感谢您一直以来对我们的支持与信任。 由于IP供应商临时发送邮件在合约到期后停止供应IP，我们不得已更换 英国地区 的IP为新的IP，目前我们已紧急租用了新的IP进行替换，以便给您提供更好的服务体验。 目前我们正在宣告新的IP地址,请关注邮件通知，感谢您的耐心等待。 受到影响的IP，您在网站的产品详情页面可以查看到弹窗提示，同时您可以点击 更换IP 按钮进行一键更换,系统将会帮您自动分配新IP，同时更换IP时您的实例将会被重启一次来配置新的IP，数据不会受到影响。 如果您的系统DD过,您需要点击更换IP之后通过VNC手动编辑网卡配置进行修正。 如果您没有在合约到期05/21/2026之前手动更换,我们会在05/21/2026帮您自动更换。 感谢您的理解和支持，如果有其他疑问，请提交服务单来联系我们 #UK IP Change Notice Hello! Thank you for your c…
❤5
香港iTech Tower 2 特价机柜 4kVA 月租 7200 HKD 。 香港荃湾数据中心整柜出租。 - 4 kVA 峰值电力。 - 月租 MRC 7200 HKD 。 - 48U Full Rack 其他收费服务 - IPv4 整段出租 0.35 USD/IP 。 - 可以提供去到 Equinix HK1 / HK2 / HK3 的 layer-2 传输服务。 有意向的老板可以联系TG： @mhdpdp
👍3
#异常通知 我们监控到 洛杉矶2节点出现故障，目前我们正在联系上游询问具体原因，请大家耐心等待。 给您带来不便深表歉意，如有其他疑问请提交服务单联系我们。 #Notification of Anomaly We have detected a malfunction at the Los Angeles2 node. We are currently contacting upstream suppliers to inquire about the specific cause. Please be patient. We sincerely apologize for any inconvenience this may cause. If you have any further questions, please submit a service request to contact us.
👍1
#维护通知 【维护通知】新加坡机房(Singapore Standard)迁移作业通知 尊敬的客户： 您好，感谢您一直以来对我们的支持与信任,我们接到上游机房的通知，为配合网络架构优化及基础设施升级计划，我们将对新加坡节点(Singapore Standard)所在机房进行整体迁移。本次调整旨在提升节点的稳定性、网络性能以及未来扩展能力，为用户提供更可靠的服务体验。 维护时间： 维护开始 2026 年 5 月 9 日 10:00（UTC+8） 预计结束 2026 年 5 月 9 日 22:00（UTC+8） 影响节点 新加坡机房(Singapore Standard) 系列 断电影响 预计持续 12小时（具体视各机柜施工进度而定） 影响说明: 在维护期间，新加坡节点相关业务将出现长时间中断。 由于本次为机房级别迁移，影响范围较大，具体恢复时间将根据实际进度逐步完成。 迁移说明: 本次迁移涉及设备下架、链路切换及新机房上线…
❤2
九年 Linux 高危漏洞于今日被披露，需要立即采取措施 安全研究公司 Xint Code（隶属 Theori）于今日公开披露了一个 Linux 内核高危漏洞，编号 为 CVE-2026-31431 命名为"Copy Fail"。漏洞根植于内核加密子系统的 algif_aead 模块，允许任何本地普通用户以确定性、无竞争的方式在任意可读文件的页缓存中写入受控的 4 字节数据，并借此将自身权限提升至 root，可以实现本地提权与容器逃逸。 漏洞成因是三个独立内核变更在 2017 年的交汇： 1. 2011 年引入的 authencesn 模块使用调用方的目标 scatterlist 作为 IPsec 扩展序列号字节重排的临时暂存区； 2. 2015 年 AF\_ALG 套接字获得 AEAD 支持，splice()路径得以将文件页缓存页直接注入 scatterlist； 3. 2017 年的一次性能优化将解密操作改为 in-pl…
❤3👍3
请大家尽快更新并重启，我们稍后也会同步我们的系统镜像。
Showing the 12 most recent of 20 posts we hold for @bagenotice. 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 — 404,869 of 1,626,935entries 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“BAGEVM 广播站” (@bagenotice), 4,350 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/bagenotice.
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.