FAQ
Frequently asked questions
How often is the feed updated?
Health status is refreshed hourly. Subscription files are refreshed every 6 hours.
Are these subscriptions public?
Yes. This repository is designed to publish public subscription artifacts and public node status output.
Which format should I choose?
Use Clash for YAML subscriptions, sing-box for JSON-based remote profiles, and V2Ray for Base64 subscription imports.
Should I use the raw link or the latest release download?
Use the raw link when your client supports auto-updating remote subscriptions. Use the latest release download when you want a stable snapshot file. For current health verification, prefer the live status page or raw status.json instead of treating the release asset as real-time state.
Has the public feed been verified?
Yes, there is a dedicated verification page that documents machine-level link checks, feed parsing checks, and the difference between raw auto-refresh links and release snapshot downloads.
Which client-specific guides are available?
Guides are available for Clash Verge Rev, FlClash, Clash Meta for Android, Hiddify Next, NekoBox, v2rayNG, and Shadowrocket.
Why keep the control plane private?
The distribution repository is public, but infrastructure state, cloud access, deployment credentials, and SSH access stay inside the private operations repository.
Why does a node stop working?
Shared public nodes can become slow or unavailable. Always compare with the live status feed before troubleshooting your client.