Telegram RegisterThe public register of Telegram
Telegram profile photo for MyAsiaCloud CDN

Channel

MyAsiaCloud CDN

@cdn_myasiacloud

On this record: Topic · Growth · Engagement · Posts · Cite this entry

19subscribers

-10 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001425259175
TypeChannel
Username@cdn_myasiacloud
CreatedBetween 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live3 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/cdn_myasiacloud

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 1 October 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 why it has no browse page of its own yet.

Growth

1929247 August 2026 — 29 subscribers11 August 2026 — 29 subscribers11 September 2026 — 24 subscribers3 October 2026 — 19 subscribers7 August 20263 October 2026
4 measurements spanning 57 days, net -10. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 18–31 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 12:1519-5
11 Sept 2026, 22:0124-5
11 Aug 2026, 05:0129no change
7 Aug 2026, 00:2429first reading

Engagement

1 post held, back to 24 June 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 1 page 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 1 post for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

24 Jun 2026, 02:31 UTC16 viewsread 11 August 2026

☁️免備案CDN ⚽️CDN加速、DDoS防禦、CC防禦一站式解决方案 👑免備案CN2中國大陸加速 ☄️穿牆節點!解决域名被移動屏蔽問題🌟 ☁️全球150+節點 💥直播、點播、APK下載、圖片、影音、遊戲、TCP端口轉發加速 🎮遊戲APP、直播APP專用—武士盾(SDK遊戲盾,無上限DDoS/CC防禦) 🌵支持websocket、特殊端口 🐳DDoS防禦無上限 ☄️CC防禦 👾USDT付款 🏂7x24技術團隊支持 😎🌍官網:www.myasiacloud.com 🌟CDN加速防禦、武士盾都可免費測試 👏聯絡商務:https://t.me/myasiacloud66 ❤️請各位認準商務ID,謹防詐騙。

Showing the 1 most recent of 1 post we hold for @cdn_myasiacloud. 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.

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 3 October 2026 — this entry's latest reading, not the date you are reading this.

“MyAsiaCloud CDN” (@cdn_myasiacloud), 19 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/cdn_myasiacloud.

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.