Telegram RegisterThe public register of Telegram
Telegram profile photo for VPS信号旗播报

Channel

VPS信号旗播报

@vps_xhq

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

49,725subscribers

+1,391 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001154242261
TypeChannel
Username@vps_xhq
DescriptionVPS新闻频道,VPS信号旗是即时发布简要讯息的小组织,关注VPS和通信自由。为你甄选最具价值的信息,提供业界热点新闻调查。 🌞 讨论群组:https://t.me/vpsxinhaoqi 🏛 评论规则:https://t.me/xhq_rule 🙋 投稿交谈:https://t.me/PandasChatBot
Created13 April 2020measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/vps_xhq

Topic

Hacking & security — 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 9 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 why it has no browse page of its own yet.

Growth

48,33449,72549,029.56 August 2026 — 48,334 subscribers6 August 2026 — 48,334 subscribers6 August 2026 — 48,342 subscribers7 August 2026 — 48,387 subscribers8 August 2026 — 48,419 subscribers9 August 2026 — 48,448 subscribers10 August 2026 — 48,544 subscribers12 August 2026 — 48,606 subscribers13 August 2026 — 48,650 subscribers14 August 2026 — 48,665 subscribers15 August 2026 — 48,722 subscribers17 August 2026 — 48,781 subscribers18 August 2026 — 48,790 subscribers19 August 2026 — 48,816 subscribers20 August 2026 — 48,854 subscribers21 August 2026 — 48,925 subscribers23 August 2026 — 48,955 subscribers24 August 2026 — 48,968 subscribers25 August 2026 — 48,987 subscribers26 August 2026 — 49,023 subscribers27 August 2026 — 49,034 subscribers28 August 2026 — 49,112 subscribers29 August 2026 — 49,158 subscribers30 August 2026 — 49,206 subscribers31 August 2026 — 49,258 subscribers1 September 2026 — 49,287 subscribers3 September 2026 — 49,338 subscribers4 September 2026 — 49,371 subscribers7 September 2026 — 49,417 subscribers10 September 2026 — 49,492 subscribers12 September 2026 — 49,572 subscribers14 September 2026 — 49,636 subscribers16 September 2026 — 49,681 subscribers18 September 2026 — 49,725 subscribers6 August 202618 September 2026
34 measurements spanning 43 days, net +1,391. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 48,125–49,934 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 12:5549,725+44
16 Sept 2026, 06:1749,681+45
14 Sept 2026, 10:0149,636+64
12 Sept 2026, 18:4249,572+80
10 Sept 2026, 22:0149,492+75
7 Sept 2026, 18:1649,417+46
4 Sept 2026, 17:2049,371+33
3 Sept 2026, 01:5649,338+51
1 Sept 2026, 20:4849,287+29
31 Aug 2026, 18:2649,258+52
30 Aug 2026, 21:4849,206+48
29 Aug 2026, 19:2549,158+46
28 Aug 2026, 18:4249,112+78
27 Aug 2026, 16:3949,034+11
26 Aug 2026, 13:3549,023+36
25 Aug 2026, 15:4748,987+19
24 Aug 2026, 17:5748,968+13
23 Aug 2026, 05:2648,955+30
21 Aug 2026, 15:4448,925+71
20 Aug 2026, 11:4848,854first reading

Engagement

25 posts held, back to 1 May 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 98 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
66.2%
avg views ÷ 49,725 subscribers
Avg views / post
32,900
3 posts measured
Reaction rate
0.747%
reactions ÷ views · ER floor
Posts in window
3
of 25 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held25 (1 May 20262 September 2026)
Views total98,800
Reactions total738
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Sept 2026, 17:38 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.

What this channel posts

Photos
25
Links
429

Lifetime counters from Telegram’s own channel header, read 23 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

6,225 reactions across 25 posts, in 51 distinct kinds. The most used accounts for 15.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😁97715.7%
💩89914.4%
🤡70111.3%
😱5999.62%
👎4367.00%
👍4156.67%
🤣3595.77%
3265.24%
🤮2924.69%
🤬2313.71%
🤯1682.70%
😨1482.38%
🔥1302.09%
🍾1051.69%
👏741.19%
😭620.996%
🖕310.498%
🌚300.482%
🥰280.45%
😡240.386%
31 further kinds1903.05%

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 25 of the 25 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 6,225 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 25 most recent posts we hold, published 1 May 2026 to 2 September 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.

Telegram Stars

Stars received
18
across the posts below
Posts paid on
7
of 25 we hold a reading for · 28%
Most on one post
6
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @vps_xhq. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 25 most recent posts we hold for this entry, published 1 May 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

2 Sept 2026, 13:56 UTC≈22,300 views287 reactionsread 23 September 2026

黑客用“免费VPS”为诱饵窃取iOS用户机密 安全研究人员在对名为“极点云PolarNode”的网页进行分析后有了一个惊人的发现,该站点所谓“免费赠送三年VPS使用权”的活动实际是黑客精心设计的陷阱。据了解,钓鱼网站在9月1日上线,黑客通过邀请码裂变方式引诱用户分发宣传链接,很快在VPS、网络运维、区块链相关论坛扩散开来。 名为 Null 的安全研究人员在 NS 论坛发布了完整的调查分析报告。据分析,攻击者利用了旧版本 iOS Safari 浏览器中的一个漏洞,访问者无需点击“同意”或下载任何安装包,仅凭苹果iPhone原生的Safari浏览器渲染网页,即可使恶意脚本静默启动。 攻击展现了罕见的工程成熟度。研究人员在解密的代码中发现了“DarkSword”与“Coruna”两套成熟利用链的痕迹。这两套过去多被商业间谍软件套件采用的高级工具,如今被黑产团伙重新分发再利用。恶意脚本通过细致的设备指纹识别,针对iOS 15.2至

😁173🤣5316😱16🤡10🆒6👏4👍3

30 Aug 2026, 01:26 UTC≈47,700 views178 reactions2 Starsread 23 September 2026

DMIT 发布关于26日网络安全事件的通报:攻击者以谋利或大规模蒸馏模型为目 DMIT 近日发布通告说明了8月26日大规模异常流量攻击事件的原委。通告称,攻击者在美东时间26日 16:00-18:00 先发送了一批试探性流量,确认出口可用后,在次日凌晨 3:00-4:00 发起了统一的大规模利用。 攻击者利用了部署在客户虚拟机上的一类 SNI 代理应用程序的设计缺陷,该类应用在处理 SNI 转发时未对请求来源与目标做有效校验。其后果是:互联网上的任意第三方,无需持有该实例的任何凭据,即可通过客户的虚拟机强制代理访问 Cloudflare 及其后端的 OpenAI 资源。运行该类应用的客户实例,实质上是一个面向全网开放的匿名 AI 请求出口。 DMIT 在探测研究后认为:攻击方大概率持有批量的"合法"API 凭据或其他有效请求来源。单纯扫描行为不会呈现这一特征。这是有预谋、有资源调度能力的行为模式,与机会主义式的滥用有本质区

🤡119👍3213🐳5🌚2👎2👾2👏1

28 Aug 2026, 02:45 UTC≈28,800 views273 reactionsread 23 September 2026

DMIT 警告称:发现大量VPS在发送异常且巨大的流量 DMIT 今天凌晨发布通告称,其主动安全系统检测到,在DMIT洛杉矶(LAX)数据中心,有2%的租户部署了具有潜在风险的应用程序。在数小时前这些租户的应用程序向中国发送了巨大的流量。DMIT初步推测,受限地区的攻击者正在大规模利用这一 TCP 443 应用程序的设计缺陷,向 OpenAI 发起超大规模的、真实的且被接受的请求。 NS论坛名为 Rayby36 的用户认为,这可能是 REALITY 协议的伪装机制与特定配置组合后被恶意利用后的结果。为了防止被网络审查系统探测,REALITY 在遇到密码错误或非法的扫描连接时,不会直接断开,而是将这些流量“回落”(即转发)给一个真实的伪装目标网站,以此假装自己是一个正常的 HTTPS 网站。许多用户将这个伪装目标设置成了 Cloudflare 等 CDN 节点上的网站。由于 CDN 节点同时服务于成千上万个网站,它具备根据请求特

👍119😁80🤣23😱1513🌚9🐳6🤬4

21 Aug 2026, 02:42 UTC≈31,800 views222 reactions1 Starread 23 September 2026

日本云计算服务商“樱花网络”客户机密数据遭泄露,波及136万个账号 8月19日,日本知名云计算与数据中心服务商樱花网络(Sakura Internet)发布安全通报称,其客户合同管理系统遭遇未授权访问。该公司业务覆盖虚拟主机、VPS、公有云及数据中心服务,此次安全事件预计波及约136万个用户账号。樱花网络在中国大陆拥有大量用户。 泄露风险数据涵盖用户的姓名、住址、联系电话、电子邮箱以及签约服务详情。初步排查发现,其中30个账号的哈希加密密码可能已被非法访问,但目前尚未最终确认相关数据是否已被黑客批量窃取外流。 8月17日,樱花网络曾通报其“Sakura Rental Server”共享主机服务在8月9日遭黑客入侵,致使583个用户账号被非法登录,部分服务器被植入恶意程序。随着技术调查的深入,团队在销售管理系统中发现了更多异常轨迹,证实客户合同管理系统早在8月9日之前就已遭渗透,直接危及系统内托管的136万会员档案。 目前

😁133🤯3714🎉7👎7🤣7😱7👏5

19 Aug 2026, 06:20 UTC≈28,400 views157 reactionsread 23 September 2026

甲骨文云开始关停超配ARM免费云主机 甲骨文云A1主机最高 4 个 OCUP + 24 GB 内存免费配额的时代已经结束。 今天,甲骨文云已经开始关停超出配额的 ARM 免费云主机。始终免费 Ampere A1 计算限制已更改为 2 个 OCPU 和 12 GB 内存。 超配主机的状态显示为“已停止”,而修改配置保存时会提示实例“已被禁用”。 [消息等级 Level C2 · 简要]

😁110👍16💩116🍾5👎2💊2🤣2

6 Aug 2026, 02:28 UTC≈36,000 views107 reactions1 Starread 23 September 2026

部分用户收到甲骨文云A1主机限期减配通知 根据Reddit、NS论坛及TG网友的反馈,从昨天开始陆续有用户收到甲骨文云的邮件。邮件称: “永久免费”计算资源的使用限制已更新。如果您的租户当前使用的“永久免费”计算资源超过了新的限制,则必须在2026 年 8 月 18 日之前减少使用量。 自2026 年 8 月 18 日起,Oracle 将开始强制执行更新后的“始终免费”计算资源限制。超出“始终免费”配额的计算实例将被自动终止。 近期,甲骨文云改变了A1 ARM实例的免费配额政策,从原先的最多4 OCUP和24GB内存削减一半至最多2 OCPU和12GB内存(同时韩国春川区域免费账户不可再创建新的 A1 计算实例)。老用户可通过编辑实例配置的方式减配。修改配置是否会导致旧版最大4Gbps的网络端口被削减未测试。 当前,只有少数用户收到了该邮件,对于是否要立即采取行动,用户应自行酌情考量。 [消息等级 Level C2 ·

👎66🍾147🌚6🤯5👍2💊2🖕2

27 Jul 2026, 10:17 UTC≈50,400 views432 reactions4 Starsread 23 September 2026

英国手机卡 Giffgaff 正对长期漫游用户采取行动 根据NS论坛的消息,Giffgaff 手机卡的运营商正在关停大量用户的服务。据停权用户反馈,他们收到了如下内容的邮件: 根据我们的条款和条件,我们的服务主要面向英国境内用户,漫游服务仅适用于短期旅行。鉴于您的使用模式表明您在英国境外长期或永久使用我们的服务,您的账户已不再符合服务资格要求。因此,您的服务将很快终止,所有相关访问权限也将停止。 Giffgaff 是一个英国移动电话公司,大量中国用户持有该公司发行的实体卡,常被用于注册海外服务。今年1月,Giffgaff 已采取过一次规模相对较小的封号行动,但恐慌情绪迅速蔓延开来。Giffgaff 和许多用户的重要服务有关联,任何风吹草动都令人惴惴不安。当前依然无法评估此次关停服务的影响规模。建议有条件的用户换绑其它运营商的手机号。 [消息等级 Level C2 · 简要]

🤮257🤡74😱35😁2111🤣8🖕7👍6

25 Jul 2026, 13:17 UTC≈45,700 views302 reactionsread 23 September 2026

中国联通香港即将限制在内地激活储值卡 中国联通香港CUniqHK发布通知称,为配合中国内地合规要求,由8月1日起,全新发行的包含中国内地漫游使用地之储值卡产品,将无法在中国内地激活启动。产品之其他服务和功能不受影响。 新卡客户需在前往中国内地前,提前在香港或此网页上所列明指定适用地区(内地除外)激活启动有关储值卡产品,成功启用服务后方可在内地使用。受影响的储值卡包括“中国内地、香港及澳门”和“中国内地及澳门”上网升级版系列,日神卡、月神卡及学神卡的升级版系列。 2025年11月,中国电信澳门率先提高了门槛,持卡人需在澳门境内认证,且不支持内地身份证。今年6月,中国移动全球数据卡也宣布不再支持于中国内地激活。所有运营商的理由皆为合规原因。这些措施限制了内地用户通过合法渠道接入国际互联网的能力。 [消息等级 Level C2 · 简要]

💩214🤡3116🤮10👎9🍾6👍6🫡4

9 Jul 2026, 12:13 UTC≈38,700 views161 reactionsread 23 September 2026

DMIT LAX AS3 系列补货 AS3是DMIT价格相对低廉的系列,十分适合对代理网络稳定性要求较高的用户,亦可以作为面向中国大陆访客网站的反向代理。 LAX.AS3.Pro.TINY $10.90/mo | $119.90/ye 1 vCPU 2 GB RAM 20 GB SSD 1Gbps/超量4Mbps无限 1000 GB 流量 1 IPv4 & 1 IPv6 /64 https://www.dmit.io/aff.php?aff=3439&pid=253 | 更高配置 · 洛杉矶Pro机型使用三网CN2回程优化,去程直连。DMIT对Pro级别的机型保证走优化线路。内地大部分省份延迟在160ms~200ms左右。 LAX.AS3.EB.TINY $10.90/mo | $119.90/ye 1 vCPU

👎10516🤮12🤔10💩7😁4🥰3🤪2

8 Jul 2026, 02:23 UTC≈34,400 views186 reactions2 Starsread 23 September 2026

高危内核虚拟机逃逸漏洞震惊云主机行业 安全研究人员昨天公开披露了 Linux 内核高危漏洞 Januscape(CVE-2026-53359)。该漏洞潜伏在 Linux 内核代码中长达 16 年之久,属于 KVM x86 架构中影子内存管理单元的“释放后重用”内存损坏漏洞。这是一项跨平台的漏洞,同时影响搭载 Intel 和 AMD 处理器的 x86 系统。 在开启了嵌套虚拟化的云端或多租户服务器上,拥有 Guest 虚拟机 Root 权限的攻击者,仅凭虚拟机内部的操作就能破坏宿主机内核的影子页状态,突破虚拟机隔离,直接在底层物理宿主机上以 Root 权限执行任意代码。 对于像 RHEL 或 CloudLinux 这样默认将 /dev/kvm 权限设置为全局可读写的系统,普通本地用户不实际运行业务虚拟机也可以通过打开该设备、创建临时 VM 来触发竞争条件实现本地提权。 漏洞对依赖 KVM 提供工作负载隔离的公有云和虚拟化集

😱137😁2112🤮4💩3👨‍💻2😍2🆒2

5 Jul 2026, 14:45 UTC≈47,000 views829 reactions6 Starsread 23 September 2026

Project X 宣布不再对抗中国GFW Xray-core 的项目团队 Project X 今日宣布“即日起完全转向俄罗斯和伊朗,严格禁止在中国大陆内使用,不再处理中国 GFW 相关事件”。Project X 将不再为对抗中国 GFW 的最新封锁而迭代,且放弃兼容中国代理软件、机场等生态。 下一个版本 REALITY 服务端还将限制客户端最小版本,并阻止“有问题的客户端” TLS 指纹。 Project X 不再面向中国用户提供服务的主要原因为“规避风险”,以及中国用户对项目捐助寥寥。公告还表达了对中国大陆代理生态现状的强烈不满。 [消息等级 Level B · #重要 ]

💩489🤣166😁48🤡43😭33💔16🥰11👎8

26 Jun 2026, 13:29 UTC≈40,900 views189 reactionsread 23 September 2026

微软削减 MS 365 开发人员版存储空间 微软 Microsoft 365 E5 开发人员版的一部分用户已在后台看到超出300GB存储限制的提示。 微软早前更新了《开发人员常见问题解答》,在该页面上新增了一个段落来说明Microsoft 365 开发人员订阅的存储空间: 租户存储上限:仅限开发人员的租户限制为 300 GB 的共用存储。 零附加存储:开发人员 SKU 在混合许可证租户中提供 0 GB SharePoint 存储。 用户 OneDrive 限制:对于开发人员 SKU 用户的 OneDrive 存储,每个用户 10 GB。 根据互联网档案馆的页面存档,微软是在今年2月或3月上旬的某个时刻更新文档的。MS 365 E5 开发人员版此前的租户上限为5TB,通过申请可扩容至25TB。微软削减OneDrive存储空间将极大地降低该订阅对“羊毛党”的吸引力。 随着今年全球计算机硬件成本不断攀升,数据中心运营成本也水涨

👎113💩367👏7😁7💊5🤯4👍3

Showing the 12 most recent of 25 posts we hold for @vps_xhq. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@vps_xhq edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
11 August 2026
Most recent edit
11 August 2026

Forward network

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.

Mentions

Named by 6 registered channels — 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.

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

风向旗参考快讯
@xhqcankao · 163,238
#1
在花🎗️科技圈
@zaihuapd · 282,472
#2
LoopDNS资讯播报
@DNSPODT · 71,856
#3
竹新社
@tnews365 · 164,267
#4
COALCLOUD(NEW)
@coalcloud · 6,021
#5
AKILE NOTICE
@akile_notice · 18,590
#6
每日消费电子观察
@CE_Observe · 74,794
#7
蓝点网订阅频道
@landiansub · 44,850
#8
特价VPS分享
@Tjjcfx · 17,877
#9
Solidot
@solidot · 47,464
#10
主机补货监控 | vps补货监控
@vps_track_share · 3,485
#11
Faker的个人频道
@wtfbugtoday · 2,971
#12
2.5次元日常 🍉
@acgdaily · 16,627
#13
BestVM公告栏
@BestVmCloud · 2,850
#14
Newlearnerの自留地
@NewlearnerChannel · 67,412
#15
层叠 - The Cascading
@outvivid · 9,009
#16
学习强国公告
@UOVZNEWS · 5,068
#17
V.PS Official Channel
@v_ps_channel · 4,899
#18
SaltyFish.IO
@SaltyFishIO · 3,824
#19
灵车漂移
@Hearse_Drifting · 10,547
#20
ᴅɪɢɪᴛᴀʟᴠɪʀᴛ ☁️ 情报站
@DigitalVirtStation · 3,754
#21
DMIT Inc - NOC工作日志
@DMIT_INC_CN · 10,783
#22
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,135
#23
PT风向旗
@Ptfxq · 17,163
#24
rvalue的生草日常
@rvalue_daily · 8,337
#25
HostEvaluate BBS
@chuanjiabaos · 2,501
#26
虚妄猫IDC_频道
@kuaileceshi2 · 3,744
#27
品测
@SIM_CN · 10,084
#28
HyperNAT 通知频道
@hypernat_channel · 2,177
#29
APPDO 数字生活指南
@AppDoDo · 40,358
#30
Sukka's Notebook
@SukkaChannel · 6,841
#31
YxVM‘s NOTICE
@yxvmcom · 2,475
#32
[24H现场直播] PoloCloud的通知
@polocloud_notification · 3,403
#33
今天abc看了啥🤔
@abcthoughts · 6,944
#34
Milkice's 生而喵喵
@milkice_portal · 3,223
#35
wap.ac
@wap_ac · 3,238
#36
HostMonit-全球主机补货通知
@hostmonit · 10,451
#37
Yummy 😋
@GodlyNews1 · 68,855
#38
Project X Channel
@projectXtls · 29,941
#39
每日沙雕墙
@woshadiao · 115,324
#40
NodeSeek新帖推送
@hostloc2tg · 4,414
#41
机场稽查局
@VPN_Police · 8,155
#42
 Apple Nuts
@AppleNuts · 37,006
#43
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 21,600
#44
希特乐乐
@NyarimeW · 5,904
#45
LetITFly News
@LetITFlyW · 9,586
#46
不存在的世界
@illusory_world · 10,974
#47
Soha 的日常
@sohadays · 4,747
#48
每日🐔juan迷惑大赏
@damm_it · 809
#49
@DocOfCard_channel - DP收录
@DocOfCard_DP · 7,678
#50
Surge TestFlight Feed
@SurgeTestFlightFeed · 12,910
#51
Miku Network Technology Channel
@miku_network_channel · 2,440
#52
你有一个打折需要了解
@SteamNy · 16,187
#53
Surge & Loon & QX 脚本收集
@NobyDa · 63,380
#54
哪吒监控公告板
@nezhanews · 3,543
#55
/var/log/DMIT-NOC.log
@DMIT_INC · 6,426
#56
Yet Another Public Notification Channel
@yapnc · 7,517
#57

Read from Telegram’s recommendation API, most recently 26 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Faker | iKun聚集地
@scriptalking · 28,154
Telegram ranks this channel #1 of 41 here — alongside 40 others — read 10 September 2026
CMLiussss 技术干货分享
@CMLiussss_channel · 67,514
Telegram ranks this channel #3 of 47 here — alongside 46 others — read 21 August 2026
风向旗参考快讯
@xhqcankao · 163,238
Telegram ranks this channel #5 of 45 here — alongside 44 others — read 12 August 2026
竹新社
@tnews365 · 164,267
Telegram ranks this channel #6 of 59 here — alongside 58 others — read 12 August 2026
蓝点网订阅频道
@landiansub · 44,850
Telegram ranks this channel #7 of 58 here — alongside 57 others — read 28 August 2026
LoopDNS资讯播报
@DNSPODT · 71,856
Telegram ranks this channel #7 of 59 here — alongside 58 others — read 20 August 2026
APPDO 数字生活指南
@AppDoDo · 40,358
Telegram ranks this channel #8 of 57 here — alongside 56 others — read 30 August 2026
看鉴中国 OutsightChina
@OutsightChina · 41,309
Telegram ranks this channel #8 of 58 here — alongside 57 others — read 29 August 2026
在花🎗️科技圈
@zaihuapd · 282,472
Telegram ranks this channel #8 of 40 here — alongside 39 others — read 12 August 2026
Solidot
@solidot · 47,464
Telegram ranks this channel #9 of 59 here — alongside 58 others — read 28 August 2026
树洞🌳群友问❓有点意思🗳
@qunyouwen · 89,462
Telegram ranks this channel #9 of 67 here — alongside 66 others — read 17 August 2026
Iyouport
@iyouport · 27,837
Telegram ranks this channel #10 of 55 here — alongside 54 others — read 10 September 2026
简中互联网废物大赏
@fucku_idiot · 40,335
Telegram ranks this channel #11 of 47 here — alongside 46 others — read 30 August 2026
Newlearnerの自留地
@NewlearnerChannel · 67,412
Telegram ranks this channel #11 of 62 here — alongside 61 others — read 21 August 2026
每日消费电子观察
@CE_Observe · 74,794
Telegram ranks this channel #11 of 62 here — alongside 61 others — read 19 August 2026
Project X Channel
@projectXtls · 29,941
Telegram ranks this channel #12 of 58 here — alongside 57 others — read 8 September 2026
【李老师不是你老师】官方电报
@lilaoshibushinilaoshi · 48,585
Telegram ranks this channel #12 of 60 here — alongside 59 others — read 26 August 2026
LINUX DO Channel
@linux_do_channel · 37,311
Telegram ranks this channel #13 of 34 here — alongside 33 others — read 1 September 2026
科学上网观察与机场测速
@jichangtj · 134,124
Telegram ranks this channel #13 of 54 here — alongside 53 others — read 15 August 2026
极客分享
@geekshare · 64,669
Telegram ranks this channel #14 of 44 here — alongside 43 others — read 21 August 2026
NodeSeek官方频道
@nodeseekc · 36,546
Telegram ranks this channel #15 of 52 here — alongside 51 others — read 2 September 2026
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,135
Telegram ranks this channel #16 of 56 here — alongside 55 others — read 15 August 2026
FREE 中文
@freechinese · 27,568
Telegram ranks this channel #17 of 55 here — alongside 54 others — read 10 September 2026
2019-nCoV疫情实时播报🅥
@nCoV2019 · 33,065
Telegram ranks this channel #17 of 59 here — alongside 58 others — read 4 September 2026

This channel appears in 70 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“VPS信号旗播报” (@vps_xhq), 49,725 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/vps_xhq.

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.