Live chat (recommended)
Best for connection or speed issues you want to work through interactively. Average queue at peak is 45 seconds.
Start a live chat →Tickets are picked up by on-duty engineers. Send the diagnostic report and we work from the actual handshake result and link-saving samples rather than reciting documentation.
Ways to reach us
Live chat when you want to iterate in real time, a ticket when you need a record — both share one case history.
Best for connection or speed issues you want to work through interactively. Average queue at peak is 45 seconds.
Start a live chat →For anything involving a report, screenshots or several people. Each ticket gets a reference number.
Submit a technical ticket →Email [email protected] and we reply within 12 hours. Include your account email and client version.
Business and private-deployment customers can book an advisor for router design reviews and bulk rollout.
[email protected] →Live chat
The session opens by collecting basic environment details, then hands over to a person. Engineers can read the diagnostic data you authorise and tell quickly whether the issue sits in your network, the exit or the configuration.
Have these ready to halve the time: operating system and client version, city and ISP, active protocol, peering point, and when the problem first appeared.
The transcript above illustrates the support flow. This page is a static demo and is not connected to the live chat service.
Open a ticket
Tickets get a reference number and a first response in about six minutes. The report contains no access records.
| Priority | First response | Resolution target |
|---|---|---|
| Critical: cannot connect | ≤ 6 minutes | ≤ 2 hours |
| High: speed or latency | ≤ 25 minutes | ≤ 8 hours |
| Normal: how-to | ≤ 2 hours | ≤ 1 business day |
| Business customers | ≤ 4 minutes | Per service agreement |
Service status
Check the table before contacting support to see whether you are hitting a regional incident. Status updates hourly.
| Region | Peering points | Average link saving | Status |
|---|---|---|---|
| Hong Kong / Taipei / Seoul | 86 | 22 ms | Operational |
| Singapore / Bangkok / Jakarta | 74 | 48 ms | Operational |
| Frankfurt / London / Paris | 92 | 172 ms | Operational |
| Los Angeles / Dallas / Toronto | 88 | 146 ms | Partial maintenance |
| Dubai / Mumbai | 41 | 118 ms | Operational |
| São Paulo / Sydney | 31 | 196 ms | Operational |
Figures are measured averages from major mainland China cities and vary with carrier and local network conditions.
Before you contact us
Live support is available in English and Chinese, and tickets and email work in either language.
An on-duty engineer takes over after the initial handshake. The system collects operating system, client version and peering point, then passes you to a person — there is no loop of canned replies.
No. A report contains the client version, protocol, handshake result, error codes and link-saving samples. It does not contain destination domains or transferred content. You can open it before sending and ask us to delete attachments at any time.
If a ticket misses its target, ask for an escalation and it moves to the senior engineer queue. If the route genuinely cannot be improved, you can request a full refund within 21 days.