Available now! Telegram Research 2025 — the year's key insights 
Surge TestFlight Feed
Open in Telegram
📈 Analytical overview of Telegram channel Surge TestFlight Feed
Channel Surge TestFlight Feed (@surgetestflightfeed) in the Chinese language segment is an active participant. Currently, the community unites 12 675 subscribers, ranking 9 949 in the Technologies & Applications category and 16 525 in the China region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 12 675 subscribers.
According to the latest data from 06 July, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 184 over the last 30 days and by 4 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 80.76%. Within the first 24 hours after publication, content typically collects 28.34% reactions from the total number of subscribers.
- Post reach: On average, each post receives 10 228 views. Within the first day, a publication typically gains 3 589 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 49.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“该频道用于提供关于 Surge iOS/Mac/tvOS 的最新 beta 版本信息”
Thanks to the high frequency of updates (latest data received on 07 July, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
12 675
Subscribers
+424 hours
+367 days
+18430 days
Posts Archive
12 675
Abort Assert Log
Surge includes a number of assert checks in its code. Assert checks are a common development and debugging mechanism used to detect situations where the program reaches a state that is different from what the developers expected.
Seeing an assert message does not necessarily mean that Surge has crashed or other issues. In many cases, the app can continue working normally, and the assert simply serves as a signal for the developers to review that part of the code.
When an assert is triggered, Surge may automatically save certain temporary logs that were previously held in memory into a log file. This is done to help developers understand what happened before the assert was triggered. This behavior is expected and should not be interpreted as abnormal memory usage or a memory leak.
Assert triggers may be seen more often in beta versions, because beta builds are designed to help identify and diagnose potential issues before a stable release.
If Surge continues to work normally, the message can usually be ignored. If you notice repeated crashes, broken functionality, or other reproducible problems together with this message, please report the issue with the relevant logs so we can investigate further
12 675
Licensing System Update
You can now deactivate an inactive device directly from the license management page on the Surge website for both Surge Mac and Surge iOS, without performing a full license reset.
* A device is considered inactive if it has not connected to the internet for more than 72 hours.
* Each license may perform this inactive-device deactivation operation once every 7 days.
* Regular device deactivation is not affected by this limitation.
12 675
Snell 6.0 beta 2
Snell v6 beta 3 has added a mode setting.
1.
mode=default Default mode, enables traffic obfuscation and AES encryption.
2. mode=unshaped Disables obfuscation and uses only AES encryption. Compared with the default mode, throughput performance can be improved by about 10%. This mode is equivalent to Snell v3, where the encrypted traffic appears completely random.
3. unsafe-raw Disables encryption and obfuscation, forwarding all traffic in plaintext. It should only be used in secure network environments, such as an intranet or under another secure tunnel.
Please note that the server mode and client mode must be consistent.12 675
Snell 6.0 beta 2
* Fixed an issue where performance unexpectedly dropped significantly
* Fixed an issue with external dynamic dependency libraries
Please note that this version adjusts the protocol profile, so Surge Mac also needs to be updated to the latest version.
12 675
Snell v6 Beta
Introduced Snell v6, featuring PSK-derived deployment-level protocol diversity that generates unique traffic characteristics for each deployment, reducing reliance on a single protocol fingerprint while preserving Snell’s core goals of performance, deployment simplicity, accurate error reporting, and full TCP semantics. Snell v6 also adds new IPv4/IPv6 network stack controls including dns-ip-preference and multi-address listen support, and is currently available for beta testing.
Please check our blog for more information: https://nssurge.com/blog/snell-v6/
12 675
Surge Mac Beta 6.7.0 now supports Tailscale as a proxy policy.
With this feature, Surge can join your Tailscale tailnet directly and route selected traffic through Tailscale peers using the existing Surge rule system. You can use Tailscale IPs, and tailnet-only services together with Surge policies, policy groups, DNS handling, traffic logging, and rule-based routing.
Please check Surge Knowledge Base for more information: https://kb.nssurge.com/surge-knowledge-base/guidelines/tailscale
12 675
A Brief Update on Surge
The Surge team has recently gone through several internal changes, and we would like to share a few updates with our users.
Support Operations
We have expanded our support operations by adding dedicated customer support staff and technical specialists.
This allows us to respond to inquiries more efficiently while keeping our engineering team focused on product development.
Communication Channels
We are currently reorganizing our external communication channels.
As part of this effort, we have launched a new official blog to share technical details about Surge and insights from our development process.
SOC 2 Alignment
We have begun aligning our internal processes with SOC 2 requirements.
This work reflects our continued investment in improving operational maturity, security practices, and overall reliability. It is especially relevant for enterprise customers with strict security and compliance expectations.
Product Development
We know many users are most interested in what’s next for Surge.
Since the official release of Surge Mac v6 on July 1, 2025, we have shipped 428 beta builds, 14 stable releases, and nearly one hundred improvements and optimizations in less than a year. The full release history is available in our release notes: https://nssurge.com/support/mac/release-notes.
At the same time, we are actively working on Tailscale integration. While we are not ready to provide a formal ETA, we expect an early beta to be available soon.
As always, our focus remains on shipping features only when they meet the standards of quality and system-level integration that users expect from Surge.
Thank you for your continued support and patience. More updates will be shared as work progresses.
https://nssurge.com/blog/a-brief-update-on-surge/
12 675
Surge Mac Tips
由于现在很多应用程序包内存在多个二进制文件，因此传统 PROCESS-NAME 规则配置需要多条才能完全匹配。
自 Surge Mac 6.0 版本开始，PROCESS-NAME 规则的用法就已经扩展，当以
/ 结尾时将进行前缀匹配，如 PROCESS-NAME,/Applications/ChatGPT.app/ 可匹配 ChatGPT.app 应用包内所有二进制。
详见：https://manual.nssurge.com/rule/process.html12 675
Surge iOS & Mac Beta 版本更新日志
• Surge Mac 版本现在可以通过 UI 编辑策略组图标，同时除了 URL 图标，也可以使用 Emoji、Surge 内置图标库和 SF Symbols。
• 策略组图标现在直接写入配置。
• iOS 版本的图标配置存储逻辑调整，现在在配置文件可编辑的情况下，将优先写入配置，以保证和 Mac 版本互通。仅当配置为只读配置时，使用独立的 UI 配置文件存储。
12 675
Surge iOS & Mac Beta 版本更新日志
- HTTP/2 CONNECT 和 TrustTunnel 代理现在支持 multiplex，由于过多子链接复用同一个 TCP 连接，可能产生性能问题，因此默认只允许最多 3 个子连接，可通过配置策略参数
max-streams 调整。12 675
关于部分历史协议维护状态的调整
以下历史协议后续将进入维护冻结状态：
* AEAD 版本之前的旧版 Shadowsocks
* TUIC v4
* VMess
相关协议的核心代码和兼容能力仍会保留，现有配置不会受到影响；但后续版本中，对应的 UI 配置入口将逐步移除。
12 675
Surge iOS & Mac Beta 版本更新日志
- 新增 HTTP/2 CONNECT 代理支持，可通过 h2-connect 类型配置基于 HTTP/2 的 CONNECT 代理连接。
- HTTP, HTTPS, HTTP/2 CONNECT, TrustTunnel 代理现支持自定义请求头，可在代理配置中使用 headers= 添加额外 header，例如：
Proxy = http, example.com, 8080, headers=X-Client:Surge;X-Token:abc Proxy = h2-connect, example.com, 443, headers=X-Padding:<random-string(16-32)>自定义 header 支持
<random-string(n)> 与 <random-string(min-max)> 占位符，连接时会自动生成 URL-safe 随机字符串，适用于需要动态 padding 或请求特征扰动的场景。12 675
关于 Surge iOS 功能更新订阅机制的调整
自 Surge iOS 推出功能更新订阅机制以来，我们一直希望在「持续演进产品能力」与「保障长期使用体验」之间保持合理的平衡。经过评估，我们决定进行如下调整：
1. 未来新增的所有代理协议兼容支持，将不再纳入功能更新订阅范围，所有用户均可直接使用。
2. 现已实验性支持的 TrustTunnel，也不会存在订阅限制，可以直接使用。
我们认为，协议兼容性应当作为长期稳定提供的基础能力，而不是阶段性的增量功能。这意味着，未来用户无需因为订阅状态，而担心基础协议支持的可用性；新的协议兼容能力也能够更直接、更持续地向所有用户开放。
调整后，订阅更新将更聚焦于新的高级功能，而协议兼容性本身，则会作为产品的长期基础能力持续维护。
与此同时，代理协议生态本身也始终处于持续变化之中。一些协议会不断演进，也有一些协议会逐渐退出主流使用场景。为了保证 Surge 长期稳定的代码库维护与整体产品质量，我们也会结合实际使用情况，对部分历史协议进入维护冻结状态，或在未来逐步结束支持。
我们会尽可能谨慎地处理相关调整，并提前进行说明，以减少对现有用户配置与使用体验的影响。
感谢大家一直以来的支持与反馈。
12 675
关于 Surge 用户交流群的说明
近期，我们多次收到与部分 Surge 用户交流群相关的邮件，包括请求协助处理群内争议、解除封禁等事项。对此，我们希望再次说明：
* 各平台上的 Surge 用户交流群均由用户自发创建和维护，Surge 团队从未参与其管理，也不具备任何控制权。
* 部分交流群中的热心用户会整理社区反馈，并转达给我们参考。这是我们了解用户意见和建议的渠道之一。但除此之外，Surge 团队与相关交流群不存在其他合作或管理关系，群内用户及管理员的言论也不代表 Surge 团队立场。
* Surge 官方讨论社区为：https://community.nssurge.com/ 。该社区仅用于技术相关的讨论与交流。该 Telegram 频道则为唯一官方公告渠道。
感谢各位的理解。
12 675
Surge iOS 5.18.0 版本已提交 App Store 审核，更新日志：
新的订阅功能：Logbook 日志簿，用于持久化记录发生的各种事件，
- 目前包含引擎启动和停止、网络切换、脚本启动和停止、脚本超时等事件
- 日志簿为脚本调试进行了特别优化，可以轻松查看脚本的输入、输出和日志。同时，脚本可以使用 $surge.logbook("content") 主动写入内容到日志本
- Surge Mac 的 Surge Dashboard 可读取远程 Surge 实例的日志簿内容，包含脚本的运行细节均可以远程直接访问
其他改进
- 为所有 TLS 相关功能（如代理协议，MITM，DoH/DoT/DoH3）新增对 X25519MLKEM768 后量子混合密钥交换组的支持
- 优化 $persistentStore 管理页面，新增搜索、导入导出、全部删除等操作
- 重构 QUIC 协议的内存管理，解决在特定情况下，QUIC-based 协议可能出现突发内存占用过高导致 Surge 被系统停止的问题
- 修正使用 Trust Tunnel 时出现的内存泄露问题
- 修正极低概率下出现的一个崩溃问题
- 修正开启 HTTP API TLS 时，API 请求可能卡住的问题
- 修正 UI 上的一些细节问题
12 675
Surge iOS/macOS Beta 更新日志
Logbook 日志簿功能现已在 Surge Mac 和 iOS 版本中加入，Logbook 用于持久化的记录事件，在 Surge 关闭后也不会丢失。（现在版本默认只保留最近 7 的事件）
- Surge Dashboard 支持读取远程实例的 Logbook 内容，同时支持查阅脚本类型记录的输入输出，以及日志输出。对端可以是 Surge iOS 或 Mac，所有内容均支持远程载入。
- Mac 版本已加入配置重载、网络切换、崩溃恢复、更新、DHCP 相关的 Logbook 写入。更多日志信息将在更新中持续加入。
12 675
使用提示
Surge Mac 6.5.0 新增了对 `compatibility-mode = 5`，非 default 路由的工作方式的支持。用于解决特定的兼容性问题（如 HomeKit Camera）。
该模式下由于 Surge VPN Interface 并非首选 Interface，因此不会修改系统的默认 DNS，但是会通过 Split DNS 机制进行 DNS 劫持。不过该机制仅对 GUI 程序有效，对 CLI 和部分 GUI 程序无效。
如果希望在该模式下依然完整劫持 DNS，请先将首选的 Interface（如 WiFi）的 DNS 修改为任意公网地址（不可使用 LAN 地址），同时再配置
hijack-dns 参数进行劫持即可。12 675
关于 Surge iOS 版本的功能订阅更新
我们了解到部分用户对近期 Surge iOS 的订阅功能更新不够频繁表示失望，因此对该问题进行说明和解决。
Surge iOS 自发布起已超过了十年，我们曾经的很多想法都已经被一个个的实现，因此，对于现在 Surge iOS 来说，想出一个新的功能并不容易。同时，为了保证用户体验，一些小型的新功能，也不会放入到订阅限制中。
对于我们的研发精力来说，其实有大量的精力放在了原有功能的改进与优化上，比如说最近更新加入的 X25519 + ML-KEM-768 后量子（混合）密钥交换支持，就要求我们从原本的 OpenSSL 实现切换至 BoringSSL，这涉及到大量的重构和测试。或是像去年跟随 Surge Mac v6 同步更新的最新 Surge VIF 引擎实现。这些都耗费了我们大量的研发精力，但是并没有纳入到订阅更新点中。
当然，由于 Surge iOS 的功能订阅，同时具备时间维度上向前与向后的延伸，我们充分理解连续订阅用户关于订阅功能点更新不够频繁的失望。因此我们建议所有用户取消自动续订开关，仅在 Surge iOS 提供了你所需要的新功能时，再进行订阅，这也是我们推出该订阅模式的初衷。即使不进行订阅，你依然可以免费享受到改进型更新，只需要为有需求的功能付费。
同时，由于我们研发人员的精力分配和开发进度的关系，我们也很难保证订阅更新的功能点可以稳定地推出，有时可能一个月就会有两个新功能，有时可能长时间都没有。因此我们现在推出一项改进，如果 Surge iOS 连续 90 天都没有推出新功能，那么在这期间存在订阅期的用户，订阅期将自动延期 90 天。
（举例来说，目前上一次订阅功能更新日是 2025 年 12 月 11 日，假如授权有效期是到 2026 年 2 月 1 日，那么订阅将自动被延期到 2026 年 5 月 1 日。）
我们将在未来数日更新授权系统进行展期，感谢您的支持和理解。
