Support runs through three channels: in-app tickets, email and Telegram. Each one suits a different kind of question, and requests are handled in the order they arrive. Below: what each channel is for, how long a reply usually takes, and a few things worth checking before you write in.
Coverage
100+ countries / 170+ routes
Refunds
60-day no-questions-asked refund
Devices
Unlimited
Payment
Alipay / WeChat Pay / USDT
01 · Channels
Three contact channels
All three channels work; what differs is the record they leave and the kind of question they suit. Anything involving orders, refunds or account changes is settled against the ticket record.
Channel · In-app·Recommended
Tickets
Account and subscription questions, orders and payments, failed subscription imports, routes that won't connect — all of it starts here. A ticket automatically carries your account and the time of submission, so you don't have to restate the background; screenshots or client logs can be attached in the same ticket.
Best for anything that needs documents attached or a longer explanation: refund requests, payment record checks, and import troubleshooting across several devices. The thread stays in your mailbox, which makes it easy to line up against a timeline later.
Best for questions a couple of lines can settle: whether a particular route is under maintenance, which protocol to pick in the client, whether a subscription link needs to be regenerated. If you need to paste logs, check an order or start a refund, go back to a ticket.
Getting the addresses: the exact email and Telegram addresses are not printed on this page, so they don't get scraped and flooded with unrelated mail. To use either channel, get the current address from the ticket entry in your dashboard first, or note in a ticket which channel you'd like the reply on.
02 · Self-check
Self-checks before you submit
A good share of connection problems can be pinned down before you ever submit anything. The four checks below take under a minute each; do them first and the reply can go straight to an actionable next step.
Four checks
Check subscription status: sign in to the dashboard and confirm the subscription is still valid and the data allowance isn't used up. Data resets monthly on the activation date, and both expiry and exhaustion look the same — “it connects but pages won't load”.
Switch routes: a region usually has several routes, and when one is under maintenance the others keep working. If switching fixes it, the problem is the route, not the account.
Check the system clock: a device clock that drifts far from real time will break subscription imports and connection setup. Turn on automatic time sync and try again.
Try another network: corporate networks and public Wi-Fi can block non-standard ports. Re-testing on a different network quickly tells you whether the problem is local or on the route.
Include these in the ticket
Your username in the dashboard, plus the order number of any related order.
Client name and version, and the operating system (Windows / macOS / iOS / Android / Linux).
The name and type of the route that failed (relay / dedicated / direct), and roughly when it happened.
The exact client error text or a screenshot — not just “it won't connect”.
03 · FAQ
FAQ
These are the questions that come up most often in tickets. Anything about pricing and refunds matches the pricing page and the refund policy page.
How soon will I get a reply after submitting a ticket?
Tickets get a first reply within 24 hours on business days, and later over public holidays. Questions that need payment records checked or a connection fault reproduced take several replies, and are handled in the order they were submitted. Please keep one ticket per issue — duplicate submissions scatter the record and actually slow things down.
How do I request a refund?
Refunds go through a ticket: submit one from your dashboard with the order number and payment method (Alipay / WeChat Pay / USDT). This service offers a 60-day no-questions-asked refund; once the order is verified it enters the refund process, and how long the money takes to arrive depends on the payment channel. The conversation for that order stays in the ticket, so later questions can just reply to it.
Where do I find the email and Telegram addresses?
The current addresses for both channels come from the ticket entry in your dashboard; they aren't listed on this page. Changes to accounts, orders and refunds are settled against the ticket record — a verbal confirmation in an instant message isn't treated as authorization.
What if a subscription import fails?
First check the subscription link is complete — chat apps often truncate long links, and it's easy to copy one segment short. Then confirm the device clock is accurate and the client is on its current version. If it still fails, paste the exact client error text, the device you're using and the route name into a ticket, and the reply will give you the matching import method.
Payment went through but the order status hasn't updated?
After an Alipay / WeChat Pay / USDT payment completes, the order status updates on the orders page in your dashboard. If it still shows unpaid after a long while, submit a ticket with a screenshot of the payment receipt and the order number, and it will be checked and handled. Don't place a second order for the same purchase.
How do I choose between a plan and a data pack?
Monthly subscriptions come in three tiers: ¥9.9/month with 60GB, ¥18/month with 250GB, and ¥28/month with 500GB. Data resets monthly on the activation date, and upgrading mid-cycle converts the price difference into the remaining days. Data packs are ¥158/300GB, ¥358/1000GB and ¥658/3000GB; they last until used up and never expire. Steady usage suits a monthly subscription; occasional heavy usage is better served by adding a data pack.
Which regions are covered, and which platforms are supported?
Coverage spans 100+ countries and 170+ routes; platforms include Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. Specific regions, cities and route types are listed by region on the global nodes page.