该异常已经恢复正常

Channel
Odyssey | 奥德赛
@odysseyCh
On this record: Growth · Engagement · Posts · Citations · Declared links · Cite this entry
24subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002001641388 |
|---|---|
| Type | Channel |
| Username | @odysseyCh |
| Created | 1 April 2024 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/odysseyCh |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 10:28 | 24 | -1 |
| 11 Aug 2026, 10:01 | 25 | no change |
| 8 Aug 2026, 10:45 | 25 | first reading |
Engagement
10 posts held, back to 1 April 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 10 posts for this entry, the most recent from 9 April 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
#网站异常 由于域名托管商-Cloudflare出现大规模异常 https://www.cloudflarestatus.com/ 我们的网站出现短暂无法访问的情况 目前客户端可正常使用,但是其它服务可能暂时中断 已手动处理部分用户的订阅恢复
我们已经最后一次完善数据库 如果仍有异常,请联系奥德赛工单客服 告知原账户和到期时间 在线客服无法及时处理 请按照以下格式: 原邮箱-原套餐-到期时间
已完全同步,如有异常,联系客服
#通知 ▎数据库二次修复 我们将于24小时内重新同步部分用户的订阅问题 频道 @OdysseyCh
#通知 ▎客户端和订阅下发异常 修复了部分地区客户端访问缓慢的问题 修复了部分地区无法订阅的问题 频道 @OdysseyCh
#通知 ▎支付时异常 修复了无法支付的问题 频道 @OdysseyCh
#节点更新 ▎美国ATT家宽节点 ▎香港HKT家宽节点 频道 @OdysseyCh
#通知 ▎O9O正式并入Odyssey 目前我们已经完成用户合并,但部分用户仍存在问题,我们仍然在恢复您的数据。 受此问题影响,您可能无法立即使用Odyssey的服务。 ▎全客户端支持 支持Windows / IOS / MacOS / Android 频道 @OdysseyCh
Channel created
Showing the 10 most recent of 10 posts we hold for @odysseyCh. 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.
Citation-graph rank
Citation-graph rank — 577,450 of 1,620,455entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
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.
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.
Declared links
2 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association— we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
https://air.odyssey.pub
https://cdn.odyssey.pub
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“Odyssey | 奥德赛” (@odysseyCh), 24 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/odysseyCh.
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.