Telegram RegisterThe public register of Telegram
Telegram profile photo for Lain_Notification

Channel

Lain_Notification

@lain_log

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

873subscribers

+1 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-1002173604853
TypeChannel
Username@lain_log
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/lain_log

Growth

8728768747 August 2026 — 872 subscribers8 August 2026 — 872 subscribers15 August 2026 — 873 subscribers23 August 2026 — 876 subscribers30 August 2026 — 873 subscribers8737 August 202630 August 2026
5 measurements spanning 23 days, net +1. 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 871–877 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 15:55873-3
23 Aug 2026, 07:37876+3
15 Aug 2026, 00:18873+1
8 Aug 2026, 01:16872no change
7 Aug 2026, 15:10872first reading

Engagement

20 posts held, back to 6 April 2026the 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
35.7%
avg views ÷ 873 subscribers
Avg views / post
312
2 posts measured
Reaction rate
1.12%
reactions ÷ views · ER floor
Posts in window
2
of 20 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. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held20 (6 April 20266 August 2026)
Views total623
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 01:16 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.

Reaction mix

8 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 62.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
562.5%
👍337.5%

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 7 of the 20 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 6 April 2026 to 6 August 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

6 Aug 2026, 09:00 UTC268 views3 reactionsread 8 August 2026

网卡更换完成。我们为宿主机跟换了Intel XL710网卡,以便更高的稳定性。VM批量开机中 如果您着急可以前往面板手动开机 The NIC replacement is complete. We replaced the bare metal with an Intel XL710 NIC to ensure greater stability. VM are bulk powering on; if you are in a hurry, you can go to the panel to start it manually. ネットワークカードの交換が完了しました。安定性を向上させるため、ホストマシンのネットワークカードをIntel XL710モデルに交換しました。 VMは起動中です。お急ぎの場合は、パネルから手動で起動することもできます。 ref: https://www.cisco.com/c/dam/en/u

👍3

5 Aug 2026, 12:24 UTC355 viewsread 8 August 2026

#通知 JP 网络维护通知 由于 JP 节点网卡异常,导致部分用户出现丢包及网络波动情况。 我们计划于 2026 年 8 月 6 日 18:00 - 19:00(日本时间 UTC+9)进行网卡更换维护。 本次维护涉及 JP BGP / JPCNT 网络。维护期间可能出现短暂网络中断、丢包、延迟升高或路由收敛等情况。 维护期间无需用户侧操作,我们将持续关注维护进度,如有变化将及时同步。 ⸻ Scheduled Network Maintenance for JP Due to a network card issue on the JP node causing packet loss and network instability for some users, scheduled maintenance will be performed. The network card replacement is pl

26 Jul 2026, 15:58 UTC633 viewsread 8 August 2026

#营销 预售 | HK / JP AMD EPYC 7663 AMD EPYC 7663 独服(Dedicated Server)预售 📍 节点:香港 🇭🇰 / 日本 🇯🇵 🖥 CPU:AMD EPYC 7663x1 112Threads 🧠 内存:256 GB DDR4(可扩展) 💾 硬盘:2 × 2 TB(可扩展) 📦 数量:预计 4 台 🚀 状态:预售 ⏳ 交付:预计 1–2 个月 ✅ 支持批量采购及定制配置 📩 咨询:@future_lain Pre-sale | HK / JP AMD EPYC 7663 AMD EPYC 7663 Dedicated Server – Pre-sale 📍 Location: Hong Kong 🇭🇰 / Japan 🇯🇵 🖥 CPU: AMD EPYC 7663x1 112Threads 🧠 Memory: 256 GB DDR4 (Upgradeable) 💾 Storage:

25 Jul 2026, 15:09 UTC603 viewsread 8 August 2026

#营销 | RIPE IP 出租 我司 RIPE IPv4 大量资源已完成入库,现正式开放出租。 产品信息 - 资源类型:IPv4,最低 /24 起租 - 资源状态:全新未使用,RIPE 管局。 - 定价:110 USDT / 月 /24,添加RPKI/改Whois不收费。 - 付款周期:季付起 长期租用客户可直接带价咨询,批量租赁或整段方案可单独沟通。 咨询联系 @farmer_lain @future_lain lain.sh #Marketing | RIPE IPv4 Leasing A large volume of our RIPE IPv4 resources has now been fully registered and is officially available for lease. Product Details - Resource type: IPv4, minimum

23 Jun 2026, 13:46 UTC≈1,320 viewsread 8 August 2026

#营销 | JPNIC IP 出租 我司 JPNIC IP 配额已完成入库,现开放出租 产品信息 - 资源类型:ipv4 /23 - 状态:全新未使用 / 未历史分配 - 定价:500USD/ 月(整 /23)起 长期租用客户可直接带价咨询 批量或整段方案可单独沟通 咨询联系: @future_lain lain.sh

20 Jun 2026, 11:57 UTC≈1,240 viewsread 8 August 2026

#通知 Starlink 日本独享线路补货 Starlink 日本独享线路现已补货,本次仅开放 1台 库存,售完即止。 产品信息 地区:日本 类型:独享线路 价格:200U / 月 特点:东京区域独立资源,非 NAT 共享,支持随机 IPv6 附加配置: - 提供 IPv6 家宽入口(用于回传优化) - 可搭配 4C4G KVM 环境 - 流量不限(合理使用) 适用场景 适用于需要独立网络环境、稳定跨境链路、以及对 Starlink 网络特性有测试需求的用户,例如业务验证、备用线路、特殊网络出口等。 注意事项 Starlink 卫星链路受天气、区域负载及轨道调度影响,延迟与路由存在正常波动。日常带宽约 300–500Mbps 区间。 开通后不支持无理由退款,请确认需求后再下单。 请注意系统可能触发基础安全审计与流量检查机制。 咨询:@farmer_lain lain.sh 售罄

8 Jun 2026, 17:02 UTC≈1,210 viewsread 8 August 2026

#营销 🔸🔸🔸🔸🔸🔸 日本家宽线路现已开启限时促销,库存有限,售完即止。 类型:🌟 Tokyo Sony Broadband 配置:4C4G AMD5950X KVM 流量:20TB / 月 ✔️首月优惠价 50 USD 优惠券: DEDIV4TYOHOME 次月起 70 USD / 月。 ✔️季度付款方案: 优惠后价格 60 USD / 月 优惠券: ERYHBFVD ✅个人用户可选择 NAT 方案。 年付仅需 60 USD 优惠码: Home-50%-off 适用场景🌐🌐🐦▶️🌐🌐✈️📞 适合日本落地节点、跨境业务部署、海外网络测试、流媒体与家宽环境需求、备用出口等场景。 🔐注意事项 家宽网络受运营商调度、区域负载及国际链路影响,路由与延迟可能存在正常波动。 优惠活动时间有限,库存售完即止,请按需购买。 审计 Lain.sh - TYO Residential NAT Audit Rules 本站无退款政策

3 Jun 2026, 23:21 UTC≈1,030 viewsread 8 August 2026
Photo

+ 08:45 Update: SONiC system upgrade start. + 08:57 Update: Almost Done!!! + 09:15 Update complete. Actual start time was 8:45 AM. Service recovery time was 9:18 AM. + Downtime: 33 mins 更新完成 lain.sh

26 May 2026, 00:14 UTC≈1,260 viewsread 8 August 2026

#通知 JPC+ 东京上游计划维护通知 接上游通知,东京节点将于 2026 年 6 月 4 日 09:00 - 12:00(日本时间 UTC+9) 进行计划内网络维护。本次维护内容包括更换 ToR(Top of Rack)交换机及升级东京核心路由器。 受影响产品为 JPC+。维护期间可能出现短暂网络中断、丢包、延迟升高或路由收敛等情况。维护期间无需用户侧操作,我们将持续关注上游维护进度,如有变化将及时同步。 ⸻ Scheduled Upstream Maintenance for JPC+ According to the upstream provider’s notice, scheduled network maintenance will be performed in Tokyo on 2026-06-04 09:00 - 12:00 JST / UTC+9. The maintenance includ

25 May 2026, 13:28 UTC962 viewsread 8 August 2026

#通知 因日本区域部分宿主机网卡出现异常,JP 区域部分 VM 可能受到影响,期间可能出现网络中断、丢包或短时不可达等情况。 我们已开始排查并处理,必要时将进行网卡更换或故障节点迁移。恢复进展将后续同步。 受影响区域:日本 JP 区域部分 VM 影响情况:可能出现网络中断、丢包、短时不可达 当前状态:正在处理中 给您带来的不便,敬请谅解。 已处理 lain.sh

16 May 2026, 04:26 UTC≈1,130 views1 reactionsread 8 August 2026
Photo

故障原因:双路电,机房维护切了一路的电,然后我们没收到预先告知email。 部分客户机器只有单路电,因此出现downtime 正在问责 Equinix 去10楼看了,告诉我:预计维护结束 May 16,2026 23:45。 如果需要将 无电的插头换到有电的,请预约200USD/Hour的smarthands。

1

16 May 2026, 03:02 UTC976 viewsread 8 August 2026

#通知 HK 区域网络故障说明 目前 HK 区域一台核心设备突发故障,导致部分业务网络出现异常波动或中断。 我方已在进行线路切换与故障隔离,预计切换完成后网络将陆续恢复。期间可能出现短暂丢包、延迟升高或连接不稳定。 请受影响用户耐心等待恢复,后续如有进一步进展将另行通知。 lain.sh 已恢复 downtime: ~45mins

Showing the 12 most recent of 20 posts we hold for @lain_log. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“Lain_Notification” (@lain_log), 873 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/lain_log.

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.