#Maintenance@HomuraNetwork 影响服务 / Related Services: ALL VPS Services 开始时间 / From: 2026-08-07 14:00 HKT 结束时间 / End: 2026-08-07 14:25 HKT 预计维护时长 / Estimated Duration: Approximately 1 hour 维护原因 / Cause: Emergency Maintenance (CVE-2026-64561) / 緊急維護(CVE-2026-64561) For details, please refer to the notification email. 詳情請參閱已發送的通知郵件。 https://status-3rd.homura.icu/r/30a4873a74e12ebdffeec57e0466135f/incident/MQxx1f7Z1ps1/

Channel
Homura Network (EN)
@HomuraNetworkEN
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
5subscribers
+0 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 | -1002017791505 |
|---|---|
| Type | Channel |
| Username | @HomuraNetworkEN |
| Created | Between 1 November 2023 and 31 December 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/HomuraNetworkEN |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 01:46 | 5 | no change |
| 7 Aug 2026, 12:24 | 5 | first reading |
Engagement
19 posts held, back to 31 December 2023 — 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.
- ERR · 30 days
- 40.0%
- avg views ÷ 5 subscribers
- Avg views / post
- 2.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 19 held
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 7 August 2026 |
|---|---|
| Posts held | 19 (31 December 2023 – 7 August 2026) |
| Views total | 4 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 01:46 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.
What this channel posts
- Photos
- 2
- Links
- 10
Lifetime counters from Telegram’s own channel header, read 13 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.
Recent posts
We recently upgraded our Looking Glass, which is now available for public testing: https://lg.homura.network You are welcome to access and use it directly. If you notice any issues with node information, network test results, or page functionality, or discover any potential security risks, please report them to us through a support ticket. We are also inviting users to participate in the beta test of our rebuilt V…
Statement Regarding Unauthorized Website Impersonation Homura Network Limited (hereinafter referred to as "the Company") has recently discovered that unauthorized domains are displaying our Company Name and Registered Office Address (RM 1805-06, 18/F, HOLLYWOOD PLAZA, 610 NATHAN ROAD, KOWLOON, HONG KONG) on their webpages without permission. The Company hereby solemnly declares that: - The Company's official websi…
https://t.me/HomuraNetwork/78
#Down 影响服务 / Related Service: HK-1 开始时间 / From: 2025-05-01 14:00 结束时间 / End : 2025-05-01 18:00(预计 Estimated) 故障原因 / Causes : Upstream Network Maintenance 更多信息/ More Info : https://t.me/KuaiCheDao_Info/3632
用戶您好, 我們收到上游通知,新加坡機房計劃將於 2025 年 4 月 13 日(星期日)凌晨 1:00(GMT +8)進行數據中心遷移維護。維護期間,您在SG-1地區的 VPS 服務將會暫時關機,預計離線時間為 1 至 3 小時。 請注意:維護期間全部服務將無法訪問與管理,且可能因上游實際情況而延長,若出現突發情況將另行通知。 維護期間不影響您的數據內容與系統設定,無需進行任何操作。但由於本次涉及服務器物理遷移,為謹慎起見,建議您提前做好資料備份。 維護給您帶來不便,我們深表歉意,並感謝您的理解與支持。如有疑問,歡迎聯繫我們。 感謝您選擇吼姆拉網絡有限公司。 Homura Network Limited 吼姆拉網絡有限公司 ------ Dear Customer, We have received notice from our upstream provider that a datacenter mi…
#Down 影响服务 / Related Service: SG-1 开始时间 / From: 2025-3-17 20:04:53 (GMT +8) 结束时间 / End : 2025-3-17 23:11 故障原因 / Causes : Upstream issues (Gateway) 更多信息/ More Info : -
#Down 影响服务 / Related Service: HK-2 开始时间 / From: 2025-01-26 20:26:59 结束时间 / End : - 故障原因 / Causes : Upstream issues (BGP) 更多信息/ More Info : https://t.me/hytronnoc/89
#非预期问题 尊敬的用户您好,我们的HK-1服务器宿主机系统出现问题,部分客户机出现无法访问的情况,因而进行紧急重启。为您带来不便深感歉意。 #Unexpected_Issue Dear Customers, there is a problem with the host system of our HK-1 server, causing some client virtual machines to freeze.We have performed an emergency restart and expect the system to recover shortly. We sincerely apologize for any inconvenience this may have caused. We deeply apologize for any inconvenience caused. We ap…
Homura Network November Promotions Thank you for your support of Homura Network over the past year! To give back to both new and existing users, we are launching an exclusive November promotional event! 📅 Event Duration: 2024.11.10 - 2024.12.1 (Asia/Hong_Kong) Promotional Details: 1️⃣ Limited-Time Discounts 🏷️ Coupon Code: AA24-HOMURA-24-1st-65-L One-time 35% discount (pay 65% of the original price), applicable…
#Unscheduled_Maintenance Dear Customers, SG-1 is scheduled for a maintenance operation at 0:00 HKT on April 15, 2024, to address certain system issues. The expected duration of the maintenance is between 45 and 60 minutes. As the system may reboot during this time, we strongly recommend backing up your data.. We appreciate your understanding and deeply apologize for any inconvenience this may cause.
Dear Customer, We have received notice from our upstream provider for HK-1 informing us of a scheduled maintenance operation from 15:00 to 22:00 HKT on Wednesday, March 6, 2024. During this maintenance window, there may be multiple instances of network disconnections. We recommend preparing in advance for this eventuality. Although user data and system status will not be affected during the maintenance, we advise ba…
Showing the 12 most recent of 19 posts we hold for @HomuraNetworkEN. 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 — 891,053 of 1,481,217entries 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 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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Homura Network (EN)” (@HomuraNetworkEN), 5 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/HomuraNetworkEN.
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.