Channel
@gephannounce
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
21,517subscribers
-698 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001492257395 |
|---|---|
| Type | Channel |
| Username | @gephannounce |
| Description | Chat: https://t.me/gephusers |
| Created | Between 1 July 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/gephannounce |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 12:55 | 21,517 | -3 |
| 4 Nov 2026, 15:49 | 21,520 | -6 |
| 3 Nov 2026, 16:56 | 21,526 | -6 |
| 2 Nov 2026, 13:48 | 21,532 | -8 |
| 1 Nov 2026, 11:58 | 21,540 | -13 |
| 31 Oct 2026, 10:10 | 21,553 | -13 |
| 30 Oct 2026, 11:05 | 21,566 | -3 |
| 29 Oct 2026, 12:06 | 21,569 | -3 |
| 28 Oct 2026, 12:46 | 21,572 | -11 |
| 27 Oct 2026, 09:35 | 21,583 | -11 |
| 26 Oct 2026, 10:36 | 21,594 | -6 |
| 25 Oct 2026, 08:40 | 21,600 | -4 |
| 24 Oct 2026, 12:06 | 21,604 | -4 |
| 23 Oct 2026, 11:00 | 21,608 | -6 |
| 22 Oct 2026, 12:05 | 21,614 | -6 |
| 21 Oct 2026, 07:34 | 21,620 | -9 |
| 20 Oct 2026, 04:39 | 21,629 | -8 |
| 19 Oct 2026, 07:20 | 21,637 | -3 |
| 18 Oct 2026, 06:59 | 21,640 | -8 |
| 17 Oct 2026, 04:27 | 21,648 | first reading |
24 posts held, back to 8 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 74 pages 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 24 posts for this entry, the most recent from 5 October 2026. An engagement rate over an empty window would be a number about nothing.
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. Below Telegram’s rounding threshold, so these counts are exact.
914 reactions across 20 posts, in 31 distinct kinds. The most used accounts for 41.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 382 | 41.8% | |
| 👍 | 166 | 18.2% | |
| 👏 | 62 | 6.78% | |
| 😨 | 55 | 6.02% | |
| 💩 | 45 | 4.92% | |
| 🙏 | 45 | 4.92% | |
| 😱 | 29 | 3.17% | |
| 🫡 | 18 | 1.97% | |
| 👎 | 15 | 1.64% | |
| 🔥 | 14 | 1.53% | |
| 🖕 | 11 | 1.20% | |
| 🤔 | 11 | 1.20% | |
| 💋 | 8 | 0.875% | |
| 🤡 | 8 | 0.875% | |
| 🤯 | 7 | 0.766% | |
| 😍 | 6 | 0.656% | |
| 🥰 | 6 | 0.656% | |
| 🎉 | 4 | 0.438% | |
| 😁 | 4 | 0.438% | |
| ✍ | 3 | 0.328% | |
| 11 further kinds | 15 | 1.64% |
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 20 of the 24 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 914 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 24 most recent posts we hold, published 8 November 2025 to 5 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.
Due to scheduled maintenance on our upstream provider’s network, Geph may experience service interruptions totaling up to one hour between October 5 at 22:00 UTC and October 6 at 06:00 UTC (October 6, 06:00–14:00 Beijing time). We apologize for the inconvenience and thank you for your patience. 由于上游服务商进行网络维护，迷雾通可能在北京时间 10 月 6 日 06:00 至 14:00 期间出现服务中断，累计最长约一小时。 给您带来的不便，我们深表歉意。感谢您的耐心与理解。
👍14❤9🔥4👎2
Signed nullchinchilla
🚨 🎉 Geph 5.9.1 is here! This update adds new domain fronts, giving Geph more ways to connect on censored networks. We’ve also improved the fallback connection path in VPN mode to help you get connected when access is restricted. Thanks for using Geph! Get 5.9.1 from geph.io / the censorship-free mirror. --- 🚨 🎉 迷雾通 5.9.1 发布啦！ 这次更新新增了域名前置线路，让迷雾通在受审查的网络中有更多连接选择。我们还改进了 VPN 模式下的备用连接方式，帮助您在网络受限时顺利连接。感谢您使用迷雾通！ 下载 5.9…
❤36🥰4🎉3👍2🙊2🫡1
Signed nullchinchilla
Geph announcements | 迷雾通通知 pinned «🚨 ⚠️ Security incident: please update to 5.9.0 and replace your account secret On September 11, an attacker used a leaked database password to access Geph's account database and copied most of it, including the login details (account secrets) of all existing…»
🚨 ⚠️ Security incident: please update to 5.9.0 and replace your account secret On September 11, an attacker used a leaked database password to access Geph's account database and copied most of it, including the login details (account secrets) of all existing accounts. No browsing history was exposed, because Geph never stores it. Anyone with your old account secret could log in to your account. Geph 5.9.0 will ask …
😨46😱21❤11🙏7👍6💩6🤡3🔥2
Signed nullchinchilla
🚨 🎉 Version 5.8.0 released — background service, kill switch & tray icon 5.8.0 is now available — one of our biggest releases since 5.0! Highlights • New background-service architecture: the VPN engine now runs as a persistent system service, so closing the window no longer disconnects you and your tunnel comes back automatically after reboot — plus a new system tray icon on Windows, macOS, and Linux. • VPN mode is…
❤47👍12👎3✍2🍾2😁2👏1😍1
Signed nullchinchilla
🆕 Version 5.7.0 released — faster multi-session connections and platform improvements 5.7.0 is now available! Highlights • Added multi-session connection support to greatly improve performance, with clearer display of active exit routes. • Updated the bundled Geph core with improved session handling, cached route reuse, and more consistent bandwidth accounting. • Added a first-run direct-connection prompt, safer se…
❤39👏22💩5🤔3❤🔥2👍2🔥2🐳1
Signed nullchinchilla
🆕 Version 5.5.0 released — lower latency and UI improvements 5.5.0 is now available! Highlights • Improved connection latency with a new one-RTT route construction algorithm. • Various UI tweaks and bugfixes. Note: This version may help users experiencing connection issues in China. Download it from geph.io or the censorship-free mirror. Note: If you downloaded Geph from Google Play, please wait for the update t…
❤24🖕10🫡6👍5💋2😍1
Signed nullchinchilla
🚨 ℹ️ China disruption update: mostly mitigated, investigation points to GFW After further investigation, this disruption appears to be originating from the Great Firewall of China. We have mitigated the issue for a large majority of our Chinese users, but we are still working on a complete solution. In the meantime, we have compensated all Plus users by 1 day. Thank you for your patience and support 🙏 --- 🚨 ℹ️ 中…
❤17🫡10👍2🔥1🤯1
Signed nullchinchilla
🚨 ⚠️ Partial service disruption in China due to traffic routing issues Geph is currently experiencing partial service disruption in China due to issues with traffic routing. Some connections may be slower, unstable, or fail temporarily ⚠️ Our team is investigating and working to restore normal routing as quickly as possible. Thank you for your patience and continued support 🙏 🚨 ⚠️ 中国境内因流量路由问题出现部分服务异常 由于流量路由问题，迷雾…
❤25🤯6🤡5👍2😭1
Signed nullchinchilla
🚨 Update: Mitigations applied — service mostly working in China We’ve deployed the first round of mitigations against the new GFW blocking, and service in China is now mostly working. Some instability may remain while we continue to improve reliability and restore full stability. As an interim measure, all Plus users affected in China have been compensated with 1 day of Plus; any remaining blocked time will be comp…
👏34❤16💩12👍9🙏3👎1🫡1
Signed nullchinchilla
Geph is currently experiencing new blocking by the Great Firewall of China. As a result, both Free and Plus service in China are temporarily disrupted ⚠️ Our team is working as quickly as possible to restore access. Thank you for your patience and continued support 🙏 After service is restored, we will compensate Plus users for all blocked time. 迷雾通目前正遭到来自中国防火长城的新一轮封锁，因此在中国境内的付费和免费版服务均暂时受到影响 ⚠️ 我们的团队正在全力以赴尽快恢复访问。感谢…
🙏32😨9❤6💩4👍1😱1
Signed nullchinchilla
⚠️ Alipay and Wechat payments are currently unstable due to instabilities in third-party payment processors we must use. The Credit Card payment method supports most Union Pay cards — we recommend using Credit Card for the time being! 💳 ⚠️ 迷雾通的支付宝/微信支付需通过第三方服务商处理，近期这些服务商不稳定，可能导致支付失败或延迟。建议您暂时选择信用卡支付。信用卡支付方式支持多数银联卡 💳
👍13😱7🤔4❤2✍1🗿1🤝1
Signed nullchinchilla
Showing the 12 most recent of 24 posts we hold for @gephannounce. 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.
Named by 2 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.
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.
Read from Telegram’s recommendation API, most recently 22 September 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.
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 1 seed channel's Telegram-generated recommendation list 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.
“Geph announcements | 迷雾通通知” (@gephannounce), 21,517 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/gephannounce.
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.