📢 Alice 免费 2TB 流量包现已支持自动领取! 不用再担心每月忘记领啦~持有适用服务器且账户状态正常的用户,系统会自动检查领取资格,并发放免费 2TB 流量包。 领取规则保持不变: • 每个账户每自然月限领 1 次,多台服务器不会重复发放。 • 每份流量包自领取起有效 30 天。 • 已有有效免费包时不会叠加领取;旧包到期且满足当月领取条件后,系统会自动补领。 • 已手动领取的不会重复发放,手动领取入口仍保留。
👍23

Channel
@AS215355_NOC
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
7,199subscribers
+459 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002062777485 |
|---|---|
| Type | Channel |
| Username | @AS215355_NOC |
| Description | root@ALICE:~# tail -f /var/log/notice.log [2023-10-23 00:00:00] ALICE Networks — Official Announcement Channel English Channel: @AS215355_NOC_EN |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/AS215355_NOC |
Other / unclassifiable — 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 12 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 23:59 | 7,199 | +5 |
| 9 Nov 2026, 11:55 | 7,194 | -6 |
| 5 Nov 2026, 18:10 | 7,200 | +14 |
| 2 Nov 2026, 18:25 | 7,186 | +7 |
| 30 Oct 2026, 09:36 | 7,179 | -2 |
| 27 Oct 2026, 17:38 | 7,181 | +17 |
| 24 Oct 2026, 18:47 | 7,164 | +22 |
| 21 Oct 2026, 12:45 | 7,142 | +15 |
| 18 Oct 2026, 08:09 | 7,127 | +32 |
| 15 Oct 2026, 08:27 | 7,095 | +35 |
| 12 Oct 2026, 01:22 | 7,060 | +54 |
| 5 Oct 2026, 09:22 | 7,006 | +63 |
| 27 Sept 2026, 08:57 | 6,943 | +53 |
| 15 Sept 2026, 10:19 | 6,890 | +22 |
| 11 Sept 2026, 21:17 | 6,868 | +37 |
| 7 Sept 2026, 01:00 | 6,831 | +36 |
| 2 Sept 2026, 13:07 | 6,795 | +19 |
| 30 Aug 2026, 15:17 | 6,776 | +18 |
| 27 Aug 2026, 13:06 | 6,758 | +23 |
| 24 Aug 2026, 03:47 | 6,735 | first reading |
26 posts held, back to 30 April 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 35 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 26 (30 April 2026 – 10 November 2026) |
| Views total | 17,340 |
| Reactions total | 64 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 16:30 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 16 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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
577 reactions across 24 posts, in 18 distinct kinds. The most used accounts for 41.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🕊 | 237 | 41.1% | |
| 👍 | 71 | 12.3% | |
| ❤ | 60 | 10.4% | |
| 👎 | 43 | 7.45% | |
| 🤡 | 40 | 6.93% | |
| 🎉 | 27 | 4.68% | |
| 😭 | 21 | 3.64% | |
| 🥰 | 18 | 3.12% | |
| 👏 | 17 | 2.95% | |
| 😱 | 14 | 2.43% | |
| 🤯 | 9 | 1.56% | |
| 🔥 | 5 | 0.867% | |
| 🤔 | 5 | 0.867% | |
| 💅 | 4 | 0.693% | |
| 👌 | 2 | 0.347% | |
| 💊 | 2 | 0.347% | |
| 🍾 | 1 | 0.173% | |
| 🙏 | 1 | 0.173% |
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 26 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 577 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 26 most recent posts we hold, published 30 April 2026 to 10 November 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: 1 of 4 posts held from the last 30 days (25.0%) 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).
📢 Alice 免费 2TB 流量包现已支持自动领取! 不用再担心每月忘记领啦~持有适用服务器且账户状态正常的用户,系统会自动检查领取资格,并发放免费 2TB 流量包。 领取规则保持不变: • 每个账户每自然月限领 1 次,多台服务器不会重复发放。 • 每份流量包自领取起有效 30 天。 • 已有有效免费包时不会叠加领取;旧包到期且满足当月领取条件后,系统会自动补领。 • 已手动领取的不会重复发放,手动领取入口仍保留。
👍23
注意防范,近期有很多恶劣入侵事件。
😱5👌2❤1
香港区域 DNS 解锁 IP 已更新,旧 DNS IP (91.103.120.36) 现已停用。 为避免国际网络异常或流媒体解锁失效,请尽快更换至新 DNS(143.246.53.4)。 快速替换命令: sed -i 's/91\.103\.120\.36/143.246.53.4/g' /etc/resolv.conf 控制面板手动更换: 可前往后台面板查看最新 DNS IP 并手动修改 /etc/reslov.conf
🥰6
娃娃没有力.rip 唯一样品.jpg (可能已经不知道去哪里了?)
😭21💅4❤2
【Alice Networks 宿主机安全维护公告】 尊敬的用户: 为修复近期披露的 Linux 内核安全漏洞,保障虚拟化平台安全,Alice Networks 计划于 2026年10月17日凌晨02:00(北京时间,UTC+8)起,对受影响的宿主机进行内核更新及重启维护。本次影响几乎是覆盖全体用户。 维护影响 - 涉及本次维护的用户虚拟机将随宿主机维护进行关机与重新启动。 - 维护期间,相关实例的网络连接及业务将暂时中断,现有连接会断开。 - 宿主机恢复后,我们将检查虚拟机启动状态,并处理启动异常。 请提前准备 - 备份重要数据,保存尚未落盘的内容。 - 避免在维护时段执行重要任务、数据库迁移或其他不宜中断的操作。 - 检查业务服务的开机自启动配置,确保虚拟机恢复后服务能够正常启动。 实际恢复时间以维护进度为准。如遇异常或维护延长,我们将另行通知。 给您带来的不便,我们深表歉意。感谢您的理解与配合。 Alice …
❤5
📢 Alice Networks|IPv4 地址迁移公告 因部分旧 IPv4 地址段即将停止使用,请受影响用户提前确认新 IP,并做好业务迁移准备。 📌 受影响的 IP 范围 本次涉及 91.103.120.0/22,包含: • 91.103.120.* • 91.103.121.* • 91.103.122.* • 91.103.123.* 如果您的服务器使用上述 IP,请按本公告完成迁移。其他 IP 不属于本次更换范围;但若业务连接、白名单或 DNS 服务器使用了上述地址,也需要检查并更新。 🗓 迁移截止时间 请于 2026 年 10 月 12 日结束前(北京时间 UTC+8)完成迁移。 10 月 12 日之后将撤除旧 IP,请勿依赖旧地址继续可用。 🔎 如何查看新 IP? 1. 登录 Alice 控制台。 2. 进入 「云服务器」,打开对应实例的详情页。 3. 找到 「IP 地址 / IP Addres…
❤1
所有未迁移实例已被删除,已关闭自助迁移入口。
🎉16🤯8👎5🍾1🥰1
注意时间,因为服务器时区问题,我们大约在中国大陆时间18:00-22:00期间开始结束迁移工作,开始后未迁移的实例将被删除。
🤔2
所有未迁移的免费机将在今天凌晨十二点后终止关闭。
🎉11👎7😱7🤯1🥰1
Alice VF原始股迁移已安排开始工作,请各位在Yuusei创建工单,以开始迁移安排工作: https://yuusei.io/tickets/new 工单格式模板(需完全一致,不按照模板创建视为放弃迁移删机): 部门选择:General 工单标题: [实例 IPv4/IPv6] 请求迁移至 Yuusei 工单内容: 我申请将以下 Alice VF 实例迁移至 Yuusei 平台。 实例信息 实例 IPv4 地址:请填写,如无请填写“无” 实例 IPv6 地址:请填写,如无请填写“无” 实例规格:xCxG(比如2c4g) Alice VF 账户邮箱:请填写 迁移确认及承诺 本人确认,本工单由 Alice VF 账户及上述实例的实际所有者本人提交,所填写的账户、实例和 IP 地址等信息均真实、准确、完整。 本人承诺不会冒用他人账户、实例或 IP 地址申请迁移。如所提供的信息存在虚假、伪造、冒用、隐瞒或其他违规情况,本人同…
🤡6❤2
由于Alice的免费机可交易性并且因为跨系统迁移原子性限制,部分用户存在迁移完成后通过删除Alice API凭据的方式阻止Yuusei删除在Alice的旧实例,因此近期不建议交易任何在Alice平台的免费叽,这部分实例将在25号被集中销毁,并且即使Push了也无法迁移至Yuusei。
🕊48👍12👎2❤1
可以迁移了 ,尽快完成。
🕊48
Showing the 12 most recent of 26 posts we hold for @AS215355_NOC. 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.
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.
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.
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 5 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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“ALICE NOTICE” (@AS215355_NOC), 7,199 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/AS215355_NOC.
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.