Hostdare 要求所有客户修改密码 有服务的及时去查看邮件修改,尤其是所有网站用同一个密码的。 官方发公告说是脚本错误,没有密码泄露 https://bill.hostdare.com/announcements/100/
👍2❤1

Channel
@vpscang
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
12,062subscribers
+329 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001134440374 |
|---|---|
| Type | Channel |
| Username | @vpscang |
| Description | VPS推荐, VPS仓补货等信息. 默认所有信息都带aff == 网站: VPS推荐: www.gubo.org VPS大全: www.vpscang.com VPS信息(自行甄别): offers.vpscang.com 群组: @guboorg 本频道仅限亲测的商家. 有需要新上商家或者促销信息请看 @liyuans (需自行甄别风险) |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/vpscang |
Ecommerce storefront — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 5 Nov 2026, 06:48 | 12,062 | +8 |
| 4 Nov 2026, 08:56 | 12,054 | +7 |
| 3 Nov 2026, 05:27 | 12,047 | +2 |
| 2 Nov 2026, 07:35 | 12,045 | +7 |
| 1 Nov 2026, 09:05 | 12,038 | +12 |
| 31 Oct 2026, 09:56 | 12,026 | +11 |
| 30 Oct 2026, 11:29 | 12,015 | +4 |
| 29 Oct 2026, 12:47 | 12,011 | +11 |
| 28 Oct 2026, 13:36 | 12,000 | +4 |
| 27 Oct 2026, 16:07 | 11,996 | +5 |
| 25 Oct 2026, 19:46 | 11,991 | +7 |
| 24 Oct 2026, 20:56 | 11,984 | -1 |
| 23 Oct 2026, 20:31 | 11,985 | +7 |
| 22 Oct 2026, 20:40 | 11,978 | +20 |
| 21 Oct 2026, 13:56 | 11,958 | +14 |
| 20 Oct 2026, 09:45 | 11,944 | +11 |
| 19 Oct 2026, 12:46 | 11,933 | +6 |
| 18 Oct 2026, 09:09 | 11,927 | +7 |
| 17 Oct 2026, 07:48 | 11,920 | +11 |
| 16 Oct 2026, 10:19 | 11,909 | first reading |
31 posts held, back to 27 May 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 52 pages of 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. It is computed over the 5 of 6 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 29 October 2026 |
|---|---|
| Posts held | 31 (27 May 2026 – 29 October 2026) |
| Views total | 35,650 |
| Reactions total | 44 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 5 Nov 2026, 07:08 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.
Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
107 reactions across 21 posts, in 2 distinct kinds. The most used accounts for 73.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 79 | 73.8% | |
| 👍 | 28 | 26.2% |
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 24 of the 31 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 107 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 27 May 2026 to 29 October 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’s own ‘edited’ marker: 4 of 6 posts held from the last 30 days (66.7%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Hostdare 要求所有客户修改密码 有服务的及时去查看邮件修改,尤其是所有网站用同一个密码的。 官方发公告说是脚本错误,没有密码泄露 https://bill.hostdare.com/announcements/100/
👍2❤1
##演示站全面关闭## 鉴于目前漏洞满天飞的情况,本频道名下所有演示站全面关闭,修复一个重新开放一个. 望周知
❤18
目前已经发现大量机器被入侵,观测到一些现象是 crontab 里面被注入了命令 类似 @reboot # fontconfig-uuid-cache /var/cache/fontconfig/.uuid-cache/fc-uuid # rtkit-prio-cache @reboot systemctl start rtkit-prio-cache.service 2>/dev/null || exec /var/lib/rtkit/.prio-cache/rtkitctl # unix-service-upd @reboot systemctl start unix-service-upd.service 2>/dev/null || exec /var/lib/unix-service/.upd-cache/usvc-updated 检查systemctl是否存在服务/etc/systemd/system/rtkit-…
❤6
PHP曝重大安全漏洞 请有重要数据的务必关注今明两天的窗口期和相关资讯 ⚠️ 核心警告:无法在代码层防御 该漏洞存在于 PHP 的底层架构中。这意味着任何代码级别的修改、面板加固或常规的应用层防护插件都无法拦截此攻击。防御的唯一有效方式是在服务器基础设施层面(环境底层)直接更新 PHP 版本。 https://t.me/ceranetworksnews/47
👍5❤1
各位多关注数据安全问题 因为AI的发展,现在网络攻击非常频繁,以前几年都不出现的最高级别高危漏洞,现在出现的频次以周或者月计,而且利用门槛都非常低。 1. 重要数据做好备份 2. 做好重要数据泄露后的应对预案 3. 最近两天会有大量主机商对宿主机进行补丁修复导致重启
👍9❤2
https://t.me/KuaiCheDao_Info/4181
Greencloudvps 取消澳洲中心-可退款可迁移 基于成本压力,将不再继续运营澳洲数据中心(9929线路),2026-12-31日全面下线。 1. 可以退款,按照剩余时间。 2. 迁移到其它数据中心+一个月补偿(原路退回,账户余额,PayPal) 3. 如果是在12月31日之前到期,那可以用到最后而不必做任何事情
❤2
DMIT HKG.AS3.EB.WEE 1 vCPU 1.0 GB RAM 20G SSD Storage 550GB Transfer 500Mbps VirtIO Interface 1 IPv4 & 1 IPv6 /64 月付24.9美金/季付74.7美金 https://www.dmit.io/aff.php?aff=184&a=add&pid=209 以下分析来源于Nanase的频道(感谢) **价格方面** 除了流量基本与Pro保持一致,各档位流量为同价格Pro的160%。 **线路方面** 去程联通/移动无优化(NTT/Lumen等),电信CN2。 回程联通CUG+CMI动态负载,移动CMI,电信163pp。 (此处有个大饼:待用户量提升后会再升级路由解决一些目前的痛点) **硬件方面** 提供AS3/AN5配置选择(7003/9005),可根据需求灵活配置。 **需要注意** 该产品线对于中国方向…
❤3
CloudIPLC - 沪日 IPLC-NAT 秒杀,中秋限时返场!🔥 - 老牌靠谱IPLC商家了 - 贵,稳,强制实名 - 可以叠加他家经常有的满赠优惠,典型的是充999赠200, 充300送40 - 对价格不敏感想要省心的可以考虑,尤其那些经常被通报下架的受害者 📅 返场时间:9/24 - 9/27 ⚙️ 配置:1vCPU / 512M / 5G-SSD / 50M 峰值带宽 ⚠️ 注意:下单后流量计划不支持变更,续费同价 💰 流量&价格: - 200G 方案:779/半年,1299/整年 - 500G 方案:2159/半年,3599/整年 - 1000G 方案:4559/半年,7599/整年 🔥 抢购链接: https://www.cloudiplc.com/aff.php?aff=202&pid=125 🌍 产品优势: - 上海国际主干,优质 BGP 多线,直连超低延时。 • 点对点真内网,加密保护,端内延迟总…
❤1
DMIT 本次补货 LAX(PRO,T1)正价套餐。 正价价格较高,非刚需建议继续等待特价。 如果追求顶级优化线路且预算充足,也建议优先选择低配套餐,性价比相对更高。 #优化线路 #CN2GIA 📦 DMIT - [LAX.AS3.Pro.TINY] 💰 $10.90 USD / Monthly BUY: https://www.dmit.io/aff.php?aff=184&a=add&pid=253 #国际线路 📦 DMIT - [LAX.AS3.T1.WEE] 💰 $36.90 USD / Annually Buy: https://www.dmit.io/aff.php?aff=184&a=add&pid=270 消息来源(感谢): https://t.me/hostmonit/50760
❤3
加利福尼亚州骨干光缆出现故障,多个本土运营商均受到影响,出现丢包、拥塞的情况 目前暂无修复 ETR https://t.me/SaltyFishIO/655
❤3
DMIT LAX AS3系列 近期最后一次补货 购买入口: LAX.AS3.Pro (1TB 10.9U/mo 起) LAX.AS3.EB (1.5TB 10.9U/mo 起) LAX.AS3.T1 (1TB单向计费 36.9U/yr 起,无中国优化)
Showing the 12 most recent of 31 posts we hold for @vpscang. 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.
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.
Named by 4 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.
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.
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.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“🥳靠谱VPS推荐(默认带aff) - VPS仓/古博” (@vpscang), 12,062 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/vpscang.
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.