伯乐网络 (cdnbl.com) 专注CDN加速(国内 香港 美国 ) 拥有 机房直营 / 24小时售后 可抗 DDOS / CC 攻击拦截 产品被黑客攻击,选择伯乐网络 有效拦截,让安全握在自己手中 在线商务 @CDN682 在线商务 @CDN682 在线商务 @CDN682

Channel
伯乐CDN 国内CDN/加速CDN/香港CDN/美国CDN
@cdn120
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
98subscribers
+0 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 | -1003570066496 |
|---|---|
| Type | Channel |
| Username | @cdn120 |
| Description | 机房直营 无视攻击 零费用测试 满意再合作 售前售后 24小时在线服务 在线客服 : @cdn682 |
| Created | 16 May 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cdn120 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:31 | 98 | no change |
| 8 Aug 2026, 02:52 | 98 | first reading |
Engagement
18 posts held, back to 16 May 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 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 18 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 11
- Links
- 9
Lifetime counters from Telegram’s own channel header, read 9 August 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.
Reaction mix
31 reactions across 10 posts, in 10 distinct kinds. The most used accounts for 29.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 9 | 29.0% | |
| ❤ | 5 | 16.1% | |
| 🔥 | 5 | 16.1% | |
| 🏆 | 3 | 9.68% | |
| 👏 | 3 | 9.68% | |
| 👎 | 2 | 6.45% | |
| 🌚 | 1 | 3.23% | |
| 🍓 | 1 | 3.23% | |
| 💯 | 1 | 3.23% | |
| 😈 | 1 | 3.23% |
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 10 of the 18 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 31reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 16 May 2026 to 21 July 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.
Recent posts
国内CDN 香港CDN 美国CDN 零费用测试 👍 全网最稳 👍 免备案 👍 免实名 👍 可测试 👍 24小时在线客服:🤩 @CDN682 🤩
🏆2🔥2
国内备案 CDN— 让你的业务跑在合规快车道上! 💡 为什么选国内CDN ✔️ 国内多地节点,毫秒级响应 ✔️ 备案域名快速接入,省时省心 ✔️支持按需扩容,业务增长无上限 🤧 安全无懈可击 稳定不宕机 始终在线 👍 全网最稳 👍 免备案 👍 免实名 👍 可测试 👍 https://t.me/CDN682
🚨 域名被污染了?换域名等于从零开始! 🧬 ┃ 域名污染处理服务 ┃ 别急着弃域!我们用技术帮你救回来 👇 ❌ 你正在经历的问题: • 域名部分地区打不开 • DNS 解析被劫持/投毒 • 换了 IP 还是无法访问 • 用户投诉"打不开网站" ✅ 我们的解决方案: DNS 智能溯源 — 精准锁定污染源头 污染节点清洗 — 逐一修复异常路由 全球路由恢复 — 重建正常解析通道 持续监控守护 — 7×24h 防止复发 💎 核心价值:保住域名 = 保住流量 = 保住钱 🌝🤩在线销售:@CDN682 🤩
https://t.me/addemoji/TIANJIAJIA8888_by_fStikBot
您的网络安全专家随时为您服务 bole cdn 专业 可靠 安全 ddos / cc 都不怕,无感拦截😀 😀:我们有自己的机房 😀:我们有专业的运维团队 😀:我们售后有24小时维护 😀:售前有24小时商务对接 😀:免费测试、满意付款 点我联系在线商务 2️⃣4️⃣😀😀😀
❤1
香港CDN 国内CDN 美国CDN ✔️7x24小时优质-售后 线路稳定-不掉包 ✔️解决移动屏蔽穿墙 不限内容 不限域名 ✔️ 不死高防CDN、过移动-屏蔽CDN、✔️亚-太无感-清洗ddos、视频-图片下载-加速类CDN 诚邀-免费测试 满意合作🤩 客服飞机😍 @CDN682
👍2🍓1👏1🔥1
国内CDN 速度更快 防御更强 800G~1T 超高防护 线路更稳 ✔️三网稳定 ✔️全国节点覆盖 ✔️屏蔽更少 ✔️持续在线 📞📞📞📞 @CDN682 售后24小时在线💙
👍2👏2
卖CDN喽 🤩 TG:@CDN682 😀免实名 😀免备案 😀不限内容 😀不限域名 😀全天24小时售后 😀机房直营,无中间商 😀无视DDOS和 CC 攻击 😀CANAME接入 简单高效(优质线路)(CN2线路) 👨💻 TG:@CDN682 😀免费测试
👍3❤1💯1🔥1
🚩🚩🚩📱📱📱📱📱 @CDN682 早买早享受 晚买没折扣 高防御 低延迟 不限域名 先用后付 售后24小时在线 点击客服联系免费接入测试
伯乐高防CDN 香港CDN 美国CDN 国内CDN 😀全天24小时售后 😀机房直营,无中间商 😀无视DDOS和 CC 攻击 😀支持网站 APK 视频 等下载加速 😀CANAME接入 简单高效(优质线路)(CN2线路) 😀国内节点 香港节点 美国节点 😀G口大带宽跑 视频、图片、apk下载 api接口 😀解决地区屏蔽 移动屏蔽 域名清洗 😀伯乐云🎉伯乐云🎉伯乐云🎉伯乐云 24小时销售TG 联系 :https://t.me/CDN682
❤1🌚1🏆1👍1🔥1😈1
我开始卖CDN了 买不买无所谓 主要是让大家有一种逛街的感觉~ 让我也有一种上班的状态~ 24小时售前售后:@CDN682
❤1
Showing the 12 most recent of 18 posts we hold for @cdn120. 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 — 201,180 of 1,584,733entries 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
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 5 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“伯乐CDN 国内CDN/加速CDN/香港CDN/美国CDN” (@cdn120), 98 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/cdn120.
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.