广东移动数据中心撤点通知 尊敬的用户,您好: 由于广东移动实行跨省结算,现深圳移动/广州移动出省被移动公司恶意限速,现决定撤销移动入口产品,涉及: - 深港移动 IEPL - 广港移动 IEPL 受影响客户将在下个月免费升级为广东电信入口,部分客户会更改成电信/联通/移动三线入口,以提升业务竞争力。 同时我们也重新开售电信深港,仅需25元/M。 以下是一份报价单供参考: 电信 25元/M 三段 联通 24元/M 三段 电信/联通/移动三线(三IP) 27元/M三段 BGP 三线(单IP) 35元/M三段 以上产品均为1G起售,如果需要更大带宽,请联系我们获取更优质报价 @nerocloudio

Channel
Rabbithosts丨日志展开......////
@rabbithostsnews
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
780subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001351102947 |
|---|---|
| Type | Channel |
| Username | @rabbithostsnews |
| Created | 26 June 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/rabbithostsnews |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 08:48 | 780 | no change |
| 11 Aug 2026, 01:46 | 780 | first reading |
Engagement
20 posts held, back to 8 April 2022 — 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 20 posts for this entry, the most recent from 29 July 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
本月第二波通报已下发,在广东的小伙伴自求多福
新一波通报已下发,各位小可爱自求多福
听说有人跑路了,可以问下 @nerocloudio 不预售无套路
我司割接^,涉及到物理割接,只丢5个包
深圳移动扩容好了,10G
尊敬的用户: 您好! 非常抱歉通知您,由于业务发展需要,将对我司深圳机房进行网络升级改造,届时将影响网络服务器质量. 维护开始时间: 2022/5/28 04:00(UTC+8) 维护终止时间: 2022/5/28 08:00 维护影响: 深圳传输业务客户将出现多次抖动,预计累积影响时间15--30min 为了避免突发情况,烦请客户提前做好应用切换等准备.
Photo, posted without a caption
深港1G虚拟机有货,滴滴 @WingsRabbit 注意事项: 移动入口跨网会有抖动,速度有,但是延迟8太行(表现为跳ping) 如果想要打游戏的话请上电信。 另外敏感期深圳移动有部署DPI,部分协议检测到就秒死,还有概率吃通报。
其实我司沪港和沪日都很不错的,并且大量有资源
现在开始所有新增订单一律进入排期状态。 所有留存订单预计最晚今日全部开通。 This is a marker point
针对:https://t.me/rabbithostsnews/692 的更新如下: Update2: 昨天于今天已累计交付10Gbps+资源,4+台独立服务器。 目前资源已剩余不多,今天订单还能实行即开即用,明日开始所有订单进入排队等待。 预计等待1week +
Showing the 12 most recent of 20 posts we hold for @rabbithostsnews. 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 — 711,146 of 1,481,306entries 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
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@rabbithostsnews named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 12 August 2026 – 12 August 2026
named in 2 posts, 12 August 2026 – 12 August 2026
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Rabbithosts丨日志展开......////” (@rabbithostsnews), 780 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/rabbithostsnews.
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.