目前,自研客户端已进入测试阶段,我们正着重优化连接稳定性、使用安全性,以及应对网络环境变化的能力。 同时也祝大家,中秋节快乐,非常感谢大家在这段时间里的支持与耐心,我们会用行动回应大家的信任。

Channel
Mitce - Notification
@Mitce_notify
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
36,022subscribers
+5,272 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002643143728 |
|---|---|
| Type | Channel |
| Username | @Mitce_notify |
| Description | 您可以在此查看Mitce的通知。 包括更新公告、維護公告、緊急情況。 You can view Mitce’s notifications here. Including update notices, maintenance notices, and urgent situations. 我们的聊天社区群组为 https://t.me/Mitce_IDGAF Our chat community group is https://t.me/Mitce_IDGAF https://mitce.net |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/Mitce_notify |
Topic
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 50% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 21:18 | 36,022 | +2,823 |
| 19 Sept 2026, 06:37 | 33,199 | +300 |
| 16 Sept 2026, 22:37 | 32,899 | +484 |
| 14 Sept 2026, 22:01 | 32,415 | +72 |
| 13 Sept 2026, 07:37 | 32,343 | +10 |
| 11 Sept 2026, 11:57 | 32,333 | +125 |
| 8 Sept 2026, 15:19 | 32,208 | +256 |
| 5 Sept 2026, 05:57 | 31,952 | +100 |
| 3 Sept 2026, 14:01 | 31,852 | +48 |
| 2 Sept 2026, 04:13 | 31,804 | +69 |
| 1 Sept 2026, 02:18 | 31,735 | +71 |
| 30 Aug 2026, 23:42 | 31,664 | +33 |
| 29 Aug 2026, 21:07 | 31,631 | +10 |
| 28 Aug 2026, 23:34 | 31,621 | -11 |
| 27 Aug 2026, 21:54 | 31,632 | +49 |
| 26 Aug 2026, 18:56 | 31,583 | +45 |
| 25 Aug 2026, 19:03 | 31,538 | +68 |
| 24 Aug 2026, 19:52 | 31,470 | +77 |
| 23 Aug 2026, 03:38 | 31,393 | +81 |
| 21 Aug 2026, 17:45 | 31,312 | first reading |
Engagement
20 posts held, back to 27 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 92 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 81.5%
- avg views ÷ 36,022 subscribers
- Avg views / post
- 29,400
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 20 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.
| Window | Rolling 30 days · latest post in window 26 September 2026 |
|---|---|
| Posts held | 20 (27 November 2025 – 26 September 2026) |
| Views total | 117,500 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Oct 2026, 19:59 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
- 16
- Videos
- 4
- Links
- 6
Lifetime counters from Telegram’s own channel header, read 3 October 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.
Recent posts
【致全体用户的重要公告】 首先,对于近期给大家带来的不便,我们致以最诚挚的歉意。 请大家放心:我们绝对不会跑路!绝对不会跑路!绝对不会跑路! 目前我们遇到了阶段性的困难,团队正在全力以赴、想方设法解决问题。恳请大家给我们一点时间,我们一定会负责到底。 同时,我们非常珍视大家的信任与耐心。等问题解决后,我们一定会拿出明确的补偿方案,绝不会让大家的等待与支持被辜负。 再次感谢大家的理解与包容,后续进展我们将第一时间向大家同步。
【维护公告】 近期由于网络环境变化及 GFW 策略调整,部分线路和节点受到影响,出现连接不稳定、节点失效或暂时无法使用等情况。 目前技术团队正在紧急排查并调整线路,全力修复受影响节点,请大家稍安勿躁,给我们一些处理时间。 我们深知,大家长期选择我们的服务,靠的是对平台稳定性和售后的信任。这次出现的问题我们不会回避,也不会让大家独自承担影响。 请大家放心,本次受到影响的用户,待服务恢复稳定后,我们会根据实际情况统一安排相应补偿。 感谢大家一直以来的理解、支持与信任。问题我们会负责到底,也一定会尽最大努力把服务恢复好,不辜负大家的信任。 修复进度及恢复情况会第一时间同步,请大家留意后续公告。
尊敬的客户,您好: 关于本次网络异常,经紧急排查,系上游 AWS 线路突发故障所致,目前同行业多家服务商均受到影响。 针对此次故障,我们与您一样十分焦急。目前技术团队已全员进入应急状态,咱们平台自己,也正全力推进内部修复与线路优化调整,尽最大努力压缩受影响时间。 预计线路将在短期内恢复,有最新进展我们将第一时间同步。给您带来的不便我们深感抱歉,感谢您的理解与配合!
关于官方网站域名更换、节点扩容及部分套餐调整的公告 1. 官网域名更换 由于部分原因,原官网域名 mitce.net 在中国大陆地区部分用户暂时无法访问。 新官网域名: mitce.io 请各位用户及合作伙伴今后使用新域名访问官网。 2. AFF 推广用户通知 请所有 AFF 推广用户尽快登录新官网重新获取新的 AFF 推广链接,并及时更新原有推广链接,以免影响推广收益。 3. 节点扩容与订阅更新 我们已完成全线节点扩容,请及时更新客户端订阅,获取最新节点列表。 ⚠️ 家宽节点提示: HK-HY2 与 TW 为住宅(家宽)节点,稳定性相对较弱,建议仅作为备用节点使用,不建议长期作为主力节点。 4. 日本优化套餐调整及补偿 受近期不可控因素影响,日本优化套餐部分节点失效,目前已暂时下架。技术团队正在积极寻找解决方案,我们会尽快恢复服务并重新上线。 补偿方案: 60G 日本优化套餐:补偿 2 USD 账户余额; 200G 日…
官网右下角点击悬浮窗,每日人工客服实时在线为大家解决问题,工作时间为9:00-18:00.
致各位用户的一封信:风雨兼程,我们始终是您的避风港 各位亲爱的用户: 近期“机场圈”动荡频繁,不少平台相继关停或失联,导致许多用户感到不安。在此,我们郑重承诺:本平台始终保持正常、稳定的运营,无论外部环境如何变化,我们都会是您最坚实的避风港。 针对近期部分用户反馈的连接问题,我们已查明原因并提供以下解决方案: 1. 日本优化套餐超时问题 目前有部分地区及运营商在使用日本优化套餐时会出现全部超时的现象。(主要为电信运营商) 解决方法: 请受影响的用户立即联系官网右下角的在线客服,我们将为您更换为网络代理套餐,即可恢复正常使用。 2. v2rayN / v2rayNG 客户端超时问题 部分使用 v2rayN 或 v2rayNG 的用户可能会遇到节点大面积超时。这通常是由于内核兼容性引起的。 解决方法 A: 在 v2rayN 设置中,将 Xray 内核切换为 Sing-box 内核。 解决方法 B: 更换为 Clash…
祝愿大家新的一年里,一马当先,马上有钱,身体健康!
由于此前配置错误问题,我们现在已经修复。 此前问题是Gemini的APP客户端地区异常,现在已经修复。 我们还在继续扩展和完善我们的解锁情况,并且在Mitce的私有内核中开发冗余解锁方案,以此确保解锁的稳定性。
CMI延迟恢复,我们还在观察。
日本节点当前运行稳定并保持可用。受 CMI 日本方向部分链路质量波动 影响,部分用户可能体验到 较平时偏高的访问延迟。我们将持续保障服务稳定性并监控相关链路状态。
当前我们确认,日本优化(东京)节点的延迟升高问题,并非由节点服务器或机房引起。 经多路径检测与链路分析,当前异常明确发生在 CMI 日本方向的国际出口链路。 该出口出现 路径绕行及互联拥塞,导致流量在出海后无法走直达日本路径,从而引发 RTT 显著升高及稳定性下降。 当前我们的节点与服务器运行状态正常,问题来源于 CMI 日本方向国际互联链路,不同接入网络受影响程度存在差异。 我们已持续监控该出口状态,并在恢复后发布新的通知。
Showing the 12 most recent of 20 posts we hold for @Mitce_notify. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“Mitce - Notification” (@Mitce_notify), 36,022 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Mitce_notify.
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.