#故障通知 HongKong - BGP KVM VPS 产品组上有一个网段存在意外的错误 导致该网段 (38.59.x.x) 在互联网不可用, 我们正在处理中。 给您带来的不便请见谅
🌭10👍6❤2👏1😱1
Channel
@network00000
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
4,639subscribers
-6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001369199366 |
|---|---|
| Type | Channel |
| Username | @network00000 |
| Created | 2 April 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/network00000 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 13:58 | 4,639 | -4 |
| 10 Aug 2026, 05:13 | 4,643 | -3 |
| 7 Aug 2026, 04:50 | 4,646 | +1 |
| 6 Aug 2026, 07:21 | 4,645 | first reading |
20 posts held, back to 11 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 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 8 April 2024. An engagement rate over an empty window would be a number about nothing.
346 reactions across 16 posts, in 13 distinct kinds. The most used accounts for 19.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 66 | 19.1% | |
| 🤯 | 59 | 17.1% | |
| ❤ | 58 | 16.8% | |
| 🌭 | 55 | 15.9% | |
| 😱 | 47 | 13.6% | |
| 🤣 | 26 | 7.51% | |
| 🌚 | 18 | 5.20% | |
| 🥰 | 7 | 2.02% | |
| 😁 | 4 | 1.16% | |
| ❤🔥 | 2 | 0.578% | |
| 🤔 | 2 | 0.578% | |
| 🎉 | 1 | 0.289% | |
| 👏 | 1 | 0.289% |
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 19 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 346reactions 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 11 November 2023 to 8 April 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
#故障通知 HongKong - BGP KVM VPS 产品组上有一个网段存在意外的错误 导致该网段 (38.59.x.x) 在互联网不可用, 我们正在处理中。 给您带来的不便请见谅
🌭10👍6❤2👏1😱1
#安全通知 TL;DR 用 ArchLinux / macOS / 追新系统版本 的可能需要关注下 有一个 Linux 系统级别的漏洞已公布,该漏洞可让攻击者无需通过 SSH 验证即可登录服务器执行任意代码 Debian/Ubuntu 的检查命令: apt list --installed 2>&1 | grep xz | grep -E '5.6.0|5.6.1' && echo "Check your system now" || echo "Everything is ok" macOS 的检查命令: brew info xz | grep xz | grep -E '5.6.0|5.6.1' && echo 'Check your system now' || echo 'Everything is ok' * 显示 Everything is ok 即不受影响 如何修复: 降级 xz-utils 即可 …
🥰7❤4👍1
Origin: https://t.me/network00000/1447 该问题出现于 Lagom 主题的下单界面。 WIKIHOST 已在下单页面时,已经添加了自动化机器人防护以及常见漏洞防护,因此早期没有发现该问题。 攻击者手动下单,通过在结算页的 Lagom 主题漏洞,向 assets/img/clients 目录上传 PHP 文件 攻击者访问上传的 PHP 文件,获取到了服务器的敏感信息。 目前, WIKIHOST 已加固财务系统的安全性,并且已经删除了攻击者上传的 PHP 文件。 并通过备份的差异对比,确认了没有其他文件被上传。 目前新增的加固措施: 1. 新增大量 WAF 规则 2. 静态资源目录将挂载为只读分区,无法新增/修改文件 3. 所有请求将只能从 WAF 通过后,才能到达后端服务器 (此前是部分请求)
❤22😱4👍3🤣2🌭1
微基主机服务 (wikihost) - idc.wiki / 原50KVM/50VZ pinned «#安全通知 TLDR: 请立即更改您的密码, 以保护您的账户、服务和系统。 涉及到的漏洞已经修复 --------------- 我们很遗憾地通知您, 我们的计费系统(idc.wiki)出现了安全漏洞 原因是我们的 Lagom 主题再修复漏洞完成后, 又发现了一个安全漏洞,导致黑客在未经授权的情况下访问了我们的数据库以及文件。 我们必须承认,在此次漏洞中访问的数据有可能被滥用。 我们无法绝对保证被访问的数据将保持安全。 因此,我们敦促您采取一切必要的预防措施来保护您的账户、服务和系统。 …»
#安全通知 TLDR: 请立即更改您的密码, 以保护您的账户、服务和系统。 涉及到的漏洞已经修复 --------------- 我们很遗憾地通知您, 我们的计费系统(idc.wiki)出现了安全漏洞 原因是我们的 Lagom 主题再修复漏洞完成后, 又发现了一个安全漏洞,导致黑客在未经授权的情况下访问了我们的数据库以及文件。 我们必须承认,在此次漏洞中访问的数据有可能被滥用。 我们无法绝对保证被访问的数据将保持安全。 因此,我们敦促您采取一切必要的预防措施来保护您的账户、服务和系统。 如果您的服务(VPS、共享主机等)账户密码与最初设置的密码不一致,请立即更改。 也请通过 idc.wiki 更改您的客户账户密码。我们对由此给您带来的不便表示诚挚的歉意。 在此期间,我们将竭尽所能为您提供帮助和支持,敬请谅解。 以下是密码安全的一些信息: IDC.wiki 账户密码: ✅ 安全 (使用 Hash 加密)…
🤯54😱29👍10❤9🌭2😁2
#故障通知 HongKong - BGP KVM VPS 网络设备已升级 新设备上出现了部分接口配置错误,导致部分宿主机公网连接中断 目前已经修复
🌭13
Origin: https://t.me/network00000/1444 维护已结束,所有 VM 正在陆续开机中 - 开始维护,所有服务器将会关机
😱13❤2🤔2👍1
#计划维护 我们将对 Japan - BGP KVM VPS / Japan - Global Only 地区进行一项计划维护,以下是维护的详细信息 维护内容: 机柜维护 维护时长: 1 - 2 小时 维护窗口: 6 小时 维护窗口开始时间: 2024/01/26 13:00 维护窗口结束时间: 2024/01/26 19:00 维护注意事项: 对机柜进行维护操作,将会导致机柜内的所有服务器断电, 我们将会在维护前关闭所有服务器,以避免数据丢失. Note: 该计划提前计划时间较短,可能对客户带来困扰,因此我们将会在维护后给予客户一定的补偿,补偿方式为:+ 3 天 使用时长
👍1
#故障通知 Korea - Ceph BGP KVM VPS - Performance 故障已解决 未知硬件问题。 我们按计划安排自助迁移功能,客户可自行选择迁移到新节点 (尚未开放,另行通知) 迁移后计算资源翻倍 (CPU/内存, CPU 将更换为 EPYC 7402p) 本次故障 SLA 故障将会在数个工作日后发放
#API 更换 Dear client: 我们已更换 IP 检测 API, 原 API 返回结果已不可靠。 您可以通过以下渠道进行检测 IP 地址是否在中国大陆可用 ICMP Ping: https://ipcheck.api.idc.wiki/ping?ip=1.1.1.1 TCP ACK Ping (Beta, 结果不可靠): https://ipcheck.api.idc.wiki/tcping?ip=1.1.1.1 返回结果结构可参考此处
👍16
Origin: https://t.me/network00000/1440 已处理完成 正在更换处理中,期间会存在断开网络情况。 断开时间取决于运维人员手速 (预计 1 - 3 分钟)
❤3👍1
#故障通知 HongKong - Standard #4 网卡故障 (间歇性不稳定) 可能导致的问题: - 间歇性几分钟与网络断开 目前近期有维护计划,另行通知.
🌭6👍1
Showing the 12 most recent of 20 posts we hold for @network00000. 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 — 1,041,269 of 1,176,251entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“微基主机服务 (wikihost) - idc.wiki / 原50KVM/50VZ” (@network00000), 4,639 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/network00000.
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.