由于香港一著名一级T1运营商(HGC)路由配置错误,导致部分网段BGP路由泄露和污染,导致全球部分网络路由混乱和大规模网络故障(主要是香港、日本、新加坡),运营商正在抢修。 路由泄露是运营商发错了“网络导航”,其他运营商信了它,导致大量用户的流量被带到错误的地方。 20点20分左右部分地区已恢复

Channel
科学上网观察与机场测速
@jichangtj
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
134,124subscribers
+969 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
Register entry
| Telegram ID | -1001406690797 |
|---|---|
| Type | Channel |
| Username | @jichangtj |
| Description | #机场推荐 #机场测速 #机场评测 /观察/点评,科学上网和科技相关新闻资讯; #机场推荐 : http://bit.ly/3fdHzbp Twitter: twitter.com/jichangtj 选机场要求很高!除非优秀否则不收。投稿要求:https://t.me/jichangtj/1014 投稿: @jichangtjBot 骚扰会ban |
| Created | 27 March 2020 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/jichangtj |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 9 August 2026 and assigned it the closest of 31 fixed categories, at 92% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 17:57 | 134,124 | +38 |
| 15 Sept 2026, 15:41 | 134,086 | +11 |
| 14 Sept 2026, 02:16 | 134,075 | +23 |
| 12 Sept 2026, 12:20 | 134,052 | +8 |
| 10 Sept 2026, 07:57 | 134,044 | +208 |
| 7 Sept 2026, 01:36 | 133,836 | +219 |
| 4 Sept 2026, 08:40 | 133,617 | +19 |
| 2 Sept 2026, 18:38 | 133,598 | +5 |
| 1 Sept 2026, 17:58 | 133,593 | +15 |
| 31 Aug 2026, 17:19 | 133,578 | -5 |
| 30 Aug 2026, 14:46 | 133,583 | +11 |
| 29 Aug 2026, 11:25 | 133,572 | +11 |
| 28 Aug 2026, 12:23 | 133,561 | -17 |
| 27 Aug 2026, 15:13 | 133,578 | +20 |
| 26 Aug 2026, 16:23 | 133,558 | +9 |
| 25 Aug 2026, 13:12 | 133,549 | -7 |
| 24 Aug 2026, 16:07 | 133,556 | -9 |
| 23 Aug 2026, 02:13 | 133,565 | +19 |
| 21 Aug 2026, 14:26 | 133,546 | +41 |
| 20 Aug 2026, 13:03 | 133,505 | first reading |
Engagement
22 posts held, back to 2 April 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 98 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 29.0%
- avg views ÷ 134,124 subscribers
- Avg views / post
- 38,900
- 4 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 4
- of 22 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 22 September 2026 |
|---|---|
| Posts held | 22 (2 April 2026 – 22 September 2026) |
| Views total | 155,500 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 22 Sept 2026, 20: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
- 406
- Videos
- 3
- Links
- 323
Lifetime counters from Telegram’s own channel header, read 22 September 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
https://x.com/fndroid/status/2098834537866514582 Clash for Windows作者Fndroid对近期出现的“Clash经典回归”App的回应。相关解释
https://huarun.win 收录代理客户端,相关开发者,内核,代理协议,翻墙历史等。得花不少时间。
📡 AWS 面向中国大陆移动、联通的网络表现较好,因此不少机场使用 AWS 作为海外中转。 自 9 月 4 日起,多家使用 AWS 中转的机场出现异常:节点在未使用时测延迟正常,TCPing 也正常,但一旦实际连接使用,该节点便会超时;Hy2 协议或ipv6目前表现正常。 有猜测认为,这可能与防火墙针对 AWS 流量的阻断有关,但也有可能是AWS路由绕路,因为以往每年AWS都会出现持续绕路几天的情况。 此外,自 8 月底起,江苏、浙江、福建部分地区的部分机场的用户反馈,使用海外 IP 中转的节点会突然长时间超时,大概率是省墙阻断。
谷歌今天推出Gemini 3.7 flash之后IP风控变严格,送中了大量IP,最明显表现为用不了Gemini。
奈云老板被抓据说是因为收款链路出现了问题,建议有推广过这家机场的更换U收款地址。
咨询了一些机场主后,了解到很多机场近几个月陆续转向 AnyTLS,主要是与通报/封锁机制有关。在今年 6 月之前,AnyTLS 基本不会因为相关原因被通报,而当时很多通报主要来自内鬼获取订阅后,然后通过程序模拟代理客户端定时拉取节点测活后再将 IP 提交导致封禁。 一种比较普遍的推测是:6 月之前,内鬼使用的测活的内核(比如xray)可能还不支持 AnyTLS,因此无法有效识别这类节点。随着 iOS 客户端陆续更新并支持 AnyTLS,越来越多机场在 5 月份开始大规模迁移到 AnyTLS,随后相关部门也在 6 月更新了测活内核(比如更换为了mihomo或singbox),因此从 6 月开始,AnyTLS 也逐渐出现了被通报的情况。 另外,目前很多机场使用的 AnyTLS 自签证书和打开跳过证书验证可能是与浙江江苏福建的SNI阻断有关系。
谷歌邮箱可以修改前缀了: http://myaccount.google.com/google-account-email 旧邮箱不影响使用,会变为备用别名邮箱。
https://youtu.be/Q5PqCkAg23I
除 #ClashMi 外。一些免费的 #IOS #ClashMeta #mihomo 内核客户端,都无广告 #Nextin 给需要封端的机场收费,普通用户免费。进入页面就是导入订阅输入框,支持扫码导入等,小白友好。开发者之前让付费发广告,想着是普通用户免费就友情推广了。 🔧 支持 HTTPS 重写(Rewrite)功能 🔗 支持链式代理(Proxy Chain) 长按节点即可设置链式出口 🧩 兼容大部分小火箭(Shadowrocket)模块规则 ▶️ 支持 YouTube 去广告模块(实验性) 下载地址 #ClashLite 超简约,图标有点萌 下载地址 #LinkClashX UI挺好 下载地址 还有:connect now , #meow (rust写的,需iOS26) #choclite(clash-rs内核) 等
由于防火墙本身的具体原理与策略外界难以得知,目前很多判断只能基于现象进行反推。因此,网络上流传的不少消息本质上都属于小道消息或个人猜测,也由此衍生出大量谣言与误读,容易误导用户,甚至引发不必要的恐慌。 建议大家保持理性判断,对相关信息尽量多方交叉验证,擦亮双眼,不轻信未经证实的传言。谣言止于智者。
观察五一之后各大 IDC 的情况后发现,封锁相比前段时间有所减弱,市场上也开始重新出现国内中转线路出售。不过,目前很多机房都会安装“傲盾”软件,用于检测翻墙流量,据称连 VLESS 在内的一些新协议也具备识别能力。 同时,部分国内中转 VPS 的价格也出现了明显上涨。此外,一些中转上游要求“押一付一”,一旦线路被通报或出现问题,押金将会被直接扣除。 目前国内中转面临的不仅是 IDC 扫描,还包括运营商侧扫描以及管局下发的封锁与整治。因此,对于机场而言,国内中转依然处于高成本、高风险的状态。 也正因为目前中转封锁依然处于较高压状态,大部分机场已尽量避开国内中转方案,比如使用直连or透传(透传入口为香港ip)。
Showing the 12 most recent of 22 posts we hold for @jichangtj. 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.
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
Named by 13 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.
@clashios · 14,11310 posts渔云𝑪𝒍𝒐𝒖𝒅𝑭𝒊𝒔𝒉𝒆𝒓
@CloudFisher · 14,6127 postsEdNovas云
@ednovasyun1 · 6,7015 posts超级索引🔍
@hao123hub · 1,0372 posts整点🐔
@tg_see · 2622 posts技术小木屋 channel
@v2rayAgentChannel · 9,3892 postsFAP18影视库(关注防丢)
@FAP18SSS · 1,6091 post•导航频道
@guantou · 9651 post科学上网机场节点
@hxcqiang · 91 postTelegram新手指引频道
@QingYun00 · 1761 postTelegram中文新手指导
@QQQCJJ · 741 postshadow
@shadow1lll · 41 post✎ 频道收录
@TGsac · 11 post
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@gebaopiCloud · 101,135#1
@ffqchannel · 62,201#2
@zaihuapd · 282,472#3
@haitun_channel · 36,991#4
@jctest6666 · 10,326#5
@jngchannel · 16,956#6
@Bronyaspeed · 9,349#7
@tkv_ktv · 2,491#8
@cheap_proxy · 25,823#9
@PinYunPs · 19,519#10
@FlClash · 46,371#11
@airport_cn · 16,101#12
@vps_xhq · 49,725#13
@jcplnanmin · 26,532#14
@ACA_Channel · 7,646#15
@Nexitally_Official · 20,790#16
@SHWLGROUP · 16,015#17
@OuONotification · 7,934#18
@xiaozhenag04 · 3,654#19
@GodlyNews1 · 68,855#20
@akile_notice · 18,590#21
@Tjjcfx · 17,877#22
@CE_Observe · 74,794#23
@DuyaoSS · 67,776#24
@KuaiCheDao_Info · 7,074#25
@me888888888888 · 50,329#26
@zhujiwiki_info · 10,687#27
@AirportAnalysis · 4,250#28
@SpeedCentrePro · 6,197#29
@zhetengsha · 49,269#30
@kuromis_xiaoxi · 13,515#31
@NewlearnerChannel · 67,412#32
@solidot · 47,464#33
@qunyouwen · 89,462#34
@Yushe_Official · 1,372#35
@PushGoodCloud · 12,034#36
@askahh · 15,137#37
@wxgqlfx · 32,872#38
@ffq_la · 3,349#39
@fullbugccc · 1,324#40
@vpscang · 11,821#41
@xhqcankao · 163,238#42
@DNSPODT · 71,856#43
@tnews365 · 164,267#44
@eggtartcloud · 1,972#45
@landiansub · 44,850#46
@woshadiao · 115,324#47
@projectXtls · 29,941#48
@NobyDa · 63,380#49
@SurgeTestFlightFeed · 12,910#50
@AppleNuts · 37,006#51
@yamby_release · 36,793#52
@surfboardnews · 28,438#53
@yapnc · 7,517#54
Read from Telegram’s recommendation API, most recently 15 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@MatsuriDayo · 45,413
Telegram ranks this channel #3 of 58 here — alongside 57 others — read 30 August 2026
@DuyaoSS · 67,776
Telegram ranks this channel #5 of 45 here — alongside 44 others — read 20 August 2026
@cheap_proxy · 25,823
Telegram ranks this channel #14 of 49 here — alongside 48 others — read 13 September 2026
@haitun_channel · 36,991
Telegram ranks this channel #16 of 39 here — alongside 38 others — read 1 September 2026
@FreeVPN8 · 44,030
Telegram ranks this channel #16 of 30 here — alongside 29 others — read 30 August 2026
@ffqchannel · 62,201
Telegram ranks this channel #24 of 45 here — alongside 44 others — read 22 August 2026
@gebaopiCloud · 101,135
Telegram ranks this channel #29 of 56 here — alongside 55 others — read 15 August 2026
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“科学上网观察与机场测速” (@jichangtj), 134,124 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/jichangtj.
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.