VPNEQ Guide: From First Login to Daily Maintenance

Chapter 1

What the service is: route structure and capability limits

Thinking of VPNEQ as “just a client” doesn't go far enough — what it actually provides is a managed cross-border route. Once you understand which segments make up that route, every later judgment about speed, stability and troubleshooting has a basis.

The three segments of a cross-border route

When you use this service to reach an overseas site, your data actually travels in three segments. The first is the entry point: the service runs access points in multiple regions, and which one your client connects to depends on the route group you select. The second is the backbone: between the access point and the exit, traffic travels over a cross-border route, and this segment determines whether peak-hour congestion will hit you. The third is the exit: traffic enters the public internet from an exit node in the target country or region, so the site sees an address at the exit location, not your original access location.

The reason to split it into three segments is that most “connected but slow” complaints trace back to the second segment, not the first. Public-internet detours and peak-hour congestion are two different sources of trouble: the first shows up as slow speeds all day with a consistently high latency; the second shows up as normal daytime performance, then jitter after 19:00 and video that keeps buffering. Telling these two apart gives your troubleshooting a direction, instead of reinstalling the client over and over.

Coverage and route types

Coverage currently spans 100+ countries / 210+ routes. Routes fall into three types, and understanding the difference between them is most of what you need to know about picking one:

• IEPL dedicated lines — end-to-end dedicated circuits that don't pass through public internet exits. They hold up best at peak hours with the smallest latency swings, and suit long video meetings, live streams and workflows that need a persistent connection.
• Relay — traffic connects to a relay point first and then exits the region, balancing cost and stability. It's the default choice in most regions and is plenty for everyday browsing and video.
• Direct — leaves the region directly from the nearest point, giving the lowest latency but the greatest exposure to public-internet quality. Best for latency-sensitive use where occasional jitter is acceptable.

Routes are grouped by region in the client: Asia / North America / Europe each form their own group, with routes sorted by city inside each group. The point of grouping is that a region usually has several routes backing each other up, so when one starts to jitter you can switch immediately instead of waiting for it to recover. For the full list of regions and cities, see the global nodes page.

Capability limits: what it does and doesn't do

Spelling out the limits is more useful than piling on adjectives. What this service does: replaces the random public-internet detours of cross-border access with controllable routes grouped by region; lets you use it on multiple devices at once at no extra charge; and lets you complete registration and subscription without an email address. What it doesn't do: it doesn't promise that any single website will be reachable 100% of the time, because sites change their own regional policies; it doesn't offer direct links to static installers — clients and subscriptions are both obtained from the dashboard after logging in; and it doesn't log browsing content, though it does keep the account and billing records it needs.

Chapter 2

Choosing a plan: three monthly tiers and data packs

Picking a tier is the only step in the whole process that requires a judgment call up front. Get it wrong and you either waste budget every month, or run out of data halfway through and have to top up in a hurry.

Estimate your monthly usage first, then pick a tier

The most common mistake is guessing based on “how much video do I watch”. A more reliable approach is to put a number on it first: ordinary office work and web browsing run about 0.1–0.3GB per hour; SD video about 0.7GB per hour; HD video about 1.5–3GB per hour; and a meeting app left running for long stretches about 0.3–0.8GB per hour. Multiply your daily hours by the hourly figure, then by 30, and you have a rough monthly total. When in doubt, round up — client background updates, system updates and cloud drive syncing are easy to forget.

The three monthly tiers compared

Data resets monthly on your activation date, not on the 1st of the calendar month. That's friendlier if you start mid-month: whatever day you activated is the day it resets from then on, so you never waste half a month's data by buying on the 15th. All three tiers are monthly subscriptions with no device limit — any number of devices can be online at once.

Data packs: use them up, they never expire

If your usage is irregular — say you only need it during two weeks of travel, or you just want to cover a temporary gap — a monthly subscription isn't necessarily the best fit. Data packs are billed by total volume, last until you use them up, have no expiry date and don't take part in the monthly reset: ¥158 / 300GB, ¥358 / 1000GB, ¥658 / 3000GB. There are two typical ways to use them: as a backstop for a monthly plan when you're running low at the end of a cycle, or as a standalone option for a low-use device that doesn't justify its own monthly tier.

How mid-cycle upgrades are calculated

Monthly subscriptions support mid-cycle upgrades. The price difference is prorated by the remaining days — you don't have to wait for the current cycle to end, and the data you've already used isn't zeroed out and recalculated. For example: upgrading from the 60GB tier to the 250GB tier means you're only charged the difference between the two tiers multiplied by the remaining days, and for the rest of the cycle you use the new tier's data allowance. Downgrades are best left until the current cycle ends, so you don't waste an allowance you've already paid for. Full details of tiers, data packs and payment are on the plans page.

Chapter 3

Sign-up and ordering: a username and password are all you need

Sign-up is deliberately short here. The reason is simple: every extra step in a flow is another place to get stuck, and verification steps are exactly the ones people get stuck on.

Sign-up needs just two things

Enter a username, set a password, done. No email address is required, so there's no “verification email never arrived” or “it went to spam” problem blocking you at step one. Your username can't be changed once set, so pick something easy to remember but hard to guess; use a password you don't reuse anywhere else. Once you're done you go straight to the user dashboard — no second confirmation.

The dashboard is a standalone page at the site root, and your login state is stored locally in the browser. Switching browsers or devices, or clearing your cache, means logging in again — that's normal and doesn't mean anything is wrong with your account. If you log in on a shared computer, sign out when you're finished.

Payment methods

Three methods are supported: Alipay, WeChat Pay and USDT. The first two suit everyday payments; USDT covers cases where those channels aren't available. After payment, the order status changes from “pending” to “paid” and the subscription is generated. If you closed the payment page quickly, just go back to the dashboard and refresh the order list — don't place the order again.

Three things to check after ordering

1. Whether the order status is “paid” — if it stays on “pending”, the payment callback hasn't completed. Refresh first, then check whether the payment channel has actually charged you.
2. Whether the overview page shows the plan as active, along with the current cycle's data allowance and reset date.
3. Whether the subscription details have appeared and can be copied. Without a subscription there's nothing to import into a client.

Once all three check out, move on to importing into your client. If the order shows as paid but the subscription still hasn't appeared, refresh the dashboard once; if it's still missing, open a ticket with the order number and the time you placed it. Don't order again while you're unsure — sorting out a duplicate payment is far more hassle than waiting for a callback.

Chapter 4

Getting your subscription: where to find the URL and how to keep it safe

From here on we're on the client side. The subscription URL is the only thing that passes between the site and your client, so understanding what it is and how much access it grants will let you work out a lot of later problems on your own.

What the subscription URL is

The subscription URL is a link with a token in it. When your client reads it, it receives a list of currently available routes and builds a local configuration from that list. It isn't the same as your account password, but it grants equivalent access: anyone who has the link can read your route list and use it directly. So treat it like a password — don't post it publicly, don't share it in group chats, and don't commit it to a public config repository.

Where to copy it

Log in to the dashboard, go to the overview page and find the subscription section. Select the client type you're using first, then copy. Different clients expect slightly different subscription formats, and the dashboard gives you the address in the right format for your selection — you don't need to assemble parameters yourself. After copying, paste it into a local text editor first to make sure there are no stray spaces or line breaks, then paste it into your client.

An example format

# Example URL (placeholder values, not usable as-is)
https://example.com/sub?token=YOUR_TOKEN

The real URL is generated by the dashboard and contains your own token. The domain and token in the example are placeholders — copying it won't work.

How often to update

The route list changes from time to time: new regions are added, routes are replaced, and nodes whose quality has dropped are retired. Most clients support automatic subscription updates — turn it on, with a daily interval. Manual updates are usually found under the client's subscription or profile management. If a region disappears from the list, update your subscription before anything else; don't rush to reinstall the client — the vast majority of “missing routes” are just a stale local list.

Subscriptions and clients are only available inside the dashboard. The site never provides direct links to static installers or a ready-to-use subscription URL.

Chapter 5

Importing into clients on five platforms, one by one

The five platforms — Windows / macOS / iOS / Android / Linux — all look different, but the import flow shares the same skeleton. Learn the skeleton first, then look at the per-platform differences; that's the fastest route.

The shared skeleton of the import flow

1. On the dashboard overview page, select the matching client type and copy the subscription URL.
2. Find the “Subscription / Profile / Server subscription” entry in your client.
3. Paste the URL and save. Some clients need you to click “Update” or “Download profile” once more.
4. Wait for the fetch to finish; routes grouped by region appear in the list.
5. Pick a route and click Connect.

These five steps hold on any platform. The differences only show up in what extra confirmation the first connection needs, and where the system is most likely to block you.

Windows

Download and install the client, open it, go to subscription management, paste the URL, save and update. When the update finishes, the list shows routes grouped into Asia, North America and Europe. On the first connection the system may ask you to confirm network permissions — just allow it. The most common trap on Windows is the system proxy switch: if the client says it's connected but your browser isn't using the route, it's usually because another program has taken over the system proxy — quit that program and reconnect. Another frequent issue is having several proxy tools installed at once; they fight over the same local port, so keep only one running at a time.

macOS

The macOS client imports subscriptions the same way. On first launch you need to allow it to add a network configuration under System Settings → Privacy & Security, otherwise the connection stays stuck at initializing. The second common macOS issue is accidentally clicking “Don't Allow” on the permission dialog — it won't appear a second time, so you have to grant it manually in System Settings.

iOS

On iOS you can't install clients from arbitrary sources — they have to come from the App Store. After importing a subscription, the system asks you to add a VPN configuration; you must allow it, or the connection can't be established. iOS takes over at the system level: once it's on, all apps' traffic goes through the route. If you only want some apps to use it, you need to set up split tunneling rules in the client — see Chapter 8. For the complete step-by-step walkthrough from scratch, including what each screen looks like, see How to use a VPN on iPhone.

Android

After downloading and installing the Android client, importing a subscription works the same as on desktop. When you connect, the system shows a “Connection request” dialog — tick “Always allow” to avoid the prompt on every reconnect. Some customized systems restrict background apps aggressively, so you'll need to whitelist the client in battery optimization; otherwise the connection gets cut after a while in the background — that's not the route dropping, it's the process being reclaimed.

Linux

On Linux the command-line client is the main option: import the subscription and start it from the terminal. It suits always-on machines or routers, where you configure once and leave it running. The CLI client's config directory is usually under your home directory — back it up before upgrading the client or switching distributions, and you can skip re-importing.

Clients for all five platforms are obtained from the download section of the dashboard, and you need to be logged in; clicking while logged out takes you to the login or subscription page.

Chapter 6

Connecting and verifying: confirming the route is really in use

“The client says connected” and “traffic is actually going through this route” are two different things. Three layers sit in between — the system proxy, split tunneling rules and caching — and if any one of them isn't working, you're effectively not connected at all.

Three steps to confirm the route is really in use

Step one: once connected, open a page that shows your current exit information and check whether the location matches the route you picked. If it doesn't, your traffic isn't going through the route — check the system proxy or your split tunneling rules first. Step two: visit a site that wouldn't load before and confirm it loads properly, rather than only the homepage opening and everything else timing out. Step three: wait ten minutes and refresh again to make sure it isn't a case of “works the moment you connect, drops right after” — if it is, the problem is most likely in the backbone, not the entry point.

What to do when the exit matches but sites still misbehave

If the exit address is correct but the site still won't open, it's usually not a route problem but the target site's own regional policy or your local cache. Order of handling: try another route in the same region first; if several routes behave exactly the same, you can safely conclude the route isn't the issue — switch to a private browser window and clear the cache, then try again. When the target site itself is down for maintenance, no route will save you.

On testing your own speed

If you want to quantify route quality, run your own comparison tests: measure off-peak and peak hours in the same period, and record latency, jitter and packet loss rather than looking at a single speed test peak. Peaks are heavily influenced by momentary congestion; it's the stability of those three metrics that reflects everyday experience. For tool choices, when to test and how to read the results, see How to test your VPN speed.

Chapter 7

Daily maintenance and renewals: data resets and refunds

Once you're connected, there are really only three things to keep an eye on: whether you have enough data, when the plan expires, and whether your subscription needs updating. All three are visible at a glance in the dashboard.

How the data reset works

Monthly subscription data resets every month on your activation date. The dashboard overview shows how much you've used this cycle and when the next reset falls. If you're running low as the reset approaches, there are two options: upgrade to a higher tier, with the difference prorated by the remaining days; or add a data pack, which lasts until you use it up and never expires, so a cycle change won't wipe it. The difference between the two: an upgrade changes your long-term allowance, while a pack only covers the stretch in front of you.

Renewals and expiry

The dashboard shows a status notice around your plan's expiry. Once it expires, routes stop working, but the subscription URL itself is kept — after renewing you don't need to re-import anything in your client; the next subscription update restores normal service. If you don't plan to renew soon after expiry, turn off automatic updates in your client to avoid repeated failed fetches.

14-day no-questions-asked refund

Within 14 days of your first payment you can request a refund, no questions asked. Use the ticket form in the dashboard and just include your order number — no reason needed and no extra proof required. Refunds go back through the original payment channel, and how long it takes depends on that channel's processing speed; the dashboard shows the refund status as it updates. This covers your first payment and is unrelated to later renewal cycles.

Three typical reasons a subscription stops working

• The client hasn't updated its subscription in a long time — the local list is stale and no longer matches the routes that are actually available. One subscription update fixes it.
• The subscription URL was regenerated in the dashboard — the old address is void. This is something you did deliberately, so just copy the new address and import it again.
• The plan expired — routes stop working. Renewing restores normal service with no re-import needed.

What all three have in common: none of them require reinstalling the client. Always check the plan status and subscription URL in the dashboard first, then look at the client.

Chapter 8

Advanced usage: split tunneling and route selection strategy

By this chapter the basics are done. What's left is turning “it works” into “it works well”: sending through the route what should go through the route, connecting directly what shouldn't, and picking the right route at different times of day.

Split tunneling: send through the route what should go through it

In the default global mode all traffic goes through the route. The upside is simplicity and nothing slipping through; the cost is that local sites take a detour too, which raises latency and burns data faster. Split tunneling decides by domain or IP what goes through the route and what connects directly. A common setup: AI tools, streaming, code hosting and overseas collaboration tools go through the route; local banking, government services, intranet systems and local services connect directly. Once the rules are active, the client list usually shows two status groups, “direct” and “proxy”, so you can check at a glance.

The most common problem with split tunneling is rule order: whichever rule matches first wins, so a broad rule placed early will swallow the precise rules after it. When adjusting rules, put specific domains first and broad rules last.

How to use the unlimited device count sensibly

There's no device limit: one account can be online on several devices at once at no extra charge. A sensible setup is to keep one always-on route for your phone and main computer, and connect tablets, spare devices and virtual machines as needed. Sharing your account with people outside it isn't recommended — once the subscription URL leaks, heavy use of the routes directly affects your own connection quality, and that usually shows up first at peak hours.

Route selection strategy

Three rules of thumb, in order of importance:

• Prefer an exit close to the target site over an access point close to you. When you're using North American services, a North American exit is usually more stable than an Asian exit that has to route around.
• At peak hours, prefer the IEPL dedicated line group. Dedicated lines don't pass through public internet exits, so they're least affected by congestion — the trade-off is fewer regions to choose from.
• Keep two routes in the same region — one for daily use, one as backup. Switching costs a single click but saves a lot of time waiting for a recovery.

Also, route quality varies by region and time of day — there's no such thing as “the one that's always fastest”. Getting into the habit of updating your subscription weekly and glancing at the list beats clinging to a single route.

How AI tools and streaming differ

These two use cases ask different things of a route. AI tools care about a stable connection that won't be reset mid-conversation; they tolerate latency well, and staying on the same route for a long time is actually more stable. Streaming cares about the exit region and sustained bandwidth — 4K playback needs steady throughput, not a momentary peak, and the exit region has to match the content library. For route-by-route comparisons and notes for each case, see AI acceleration and global nodes.

Chapter 9

Troubleshooting quick reference: symptoms, causes and what to try first

This chapter gathers the failure points from earlier chapters into one quick-reference table. When something goes wrong, look it up by symptom and try the steps in order — don't skip ahead.

Order of handling: switch routes first, then clients, and open a ticket last

The worst thing you can do in troubleshooting is reinstall the client straight away. The right order: switch to another route in the same region to see whether it's a single-route problem; then try another device or client to see whether it's a problem with your own setup; only after ruling both out should you open a ticket. When you do, include everything — platform, client name, route name, when the problem appeared, and what you've already tried. A complete ticket usually gets diagnosed in one round; a ticket that just says “can't connect” takes several rounds.

Three situations that are easy to misdiagnose

• The target site itself is down for maintenance — nothing to do with the route; switching routes won't change a thing. Try another site in the same region to confirm.
• Your local network restricts outbound traffic — common in hotels, airports and corporate networks. Switching routes won't help here; see testing hotel Wi-Fi on a business trip for how to handle it.
• The browser cached the earlier failure — after switching routes you need a hard refresh or a private window, otherwise you'll still be looking at the previous failure page.

When you must open a ticket

Three situations where you shouldn't keep retrying on your own: several routes in the same region are all unavailable for more than ten minutes; an order shows as paid but the subscription never appears; or you need to request a refund. The ticket form is inside the user dashboard — include your order number and when the problem started and it'll be handled much faster. In all other cases, work through the checks above first; you can usually solve it yourself.

Next steps

Three paths after reading

That's the end of the guide. Where you go next depends on which step you're at.

• Not signed up yet — start with the plans page to compare the three monthly tiers and data packs, then register and order from the dashboard once you've picked a tier. No email address is needed — a username and password are enough.
• Signed up and importing into a client — go back to Chapter 5 and find your platform, or follow the step-by-step instructions in Quick Start.
• Been using it for a while — focus on Chapters 7 and 8: data resets, prorated upgrades, split tunneling and route selection strategy. These have the biggest effect on day-to-day experience.

If you still have questions after reading the guide, the help center categories and the ticket form are two parallel channels: check the help center for common questions first, and use the dashboard ticket form for anything to do with your account, orders or refunds.

VPNEQ · 100+ countries / 210+ routes · Unlimited devices · 14-day no-questions-asked refund