VPN40 / TROUBLESHOOTING

VPN Troubleshooting Guide

First distinguish between your local network, subscription status, proxy routing and the destination service. Change one setting at a time and keep notes that make the issue reproducible.

Windows / macOS / iOS / Android / Linux Unlimited devices 7-day no-questions-asked refund

This page is a troubleshooting reference for existing users; it does not replace the initial setup guide. If you haven’t installed a client and imported your subscription yet, start with Quick Start. Once you encounter an error, find the closest symptom below. You don’t need to share your password or full subscription URL during troubleshooting.

Can’t connect at all: establish a baseline

“Can’t connect” could mean the client won’t start, the Connect button returns an error, or a particular website won’t load. First note exactly what happens: Does the client say it’s running? Can you select a route? Does your browser show a certificate warning, or does it keep waiting for a response? Don’t assume every symptom points to a route problem. A connected status only means the local connection process reached a certain state; it doesn’t prove that your request reached its destination and returned successfully.

Check your local network without the proxy first

Save anything you’re working on, disconnect the client, and visit a site you can normally access directly. If it still won’t load, check that your Wi-Fi is connected to the internet, your Ethernet cable is secure and your router is working. On hotel or public Wi-Fi, your device may be connected to the hotspot but still need to complete a browser-based sign-in. Sign in through a regular browser before reconnecting the proxy, so the login request isn’t sent through a connection that hasn’t been established yet.

Once your local network is working, keep the same device, browser and destination page, and connect only to the currently selected route. If it immediately returns an error, note the exact message before continuing. An incorrect system clock can cause certificate validation to fail; enable automatic time and check your time zone. Don’t ignore a certificate warning to “fix” the connection. That can hide the real cause and expose your account credentials to an untrusted page.

Check client permissions and the route handshake separately

Check that the client has the network permissions required by your system and that the relevant proxy mode is enabled. On desktop, the system proxy and a virtual network interface aren’t the same thing. On mobile, you may need to approve the network connection prompt shown by the system. If you previously denied permission, check it in system settings, then return to the client and reconnect. Option names vary by client version, so don’t look for a setting based on screenshots of other software.

If another proxy, corporate networking client or traffic-filtering tool is running on the device, check whether it’s competing for the same system settings. On a personal device that you’re allowed to configure, you can temporarily quit other connection tools to compare results. For a managed work device, contact your administrator instead of removing corporate settings. Closing a browser window doesn’t necessarily stop a proxy running in the background; check the system tray or active processes to confirm its status.

Use comparison tests to narrow down the cause

If the current route fails, try another available route in the same region, then try a different region if it still fails. The goal isn’t to keep guessing; it’s to find out whether the issue is specific to one path. If switching routes fixes it, note the original route name and the time of the failure. If every route fails but your direct connection works, check your subscription, client permissions and local network filters first. See the route list for information about route types; names alone don’t predict performance.

If possible, connect the same device to another trusted network and repeat the same test. If switching networks fixes the issue, investigate the original network’s access policies or route. If other devices on the same network work, the problem is more likely to be with this device’s configuration. Write down the result after each comparison. Don’t change the network, client and route all at once, or you won’t know which change helped.

Submit a support ticket when your direct connection and account are working, client permissions are confirmed, and routes in different regions return the same handshake error. Include the exact error, when it occurred, your network type and the results of your comparison tests. Don’t uninstall the app or wipe all settings just to “be thorough”; original logs and a reproducible issue are usually more useful than repeated reinstalls.

Connected but websites won’t load: check DNS and the request path

If a website won’t load after connecting, distinguish between DNS resolution, establishing a connection and the app’s response. A “server not found” message may point to DNS. A connection timeout could mean the request isn’t going through the expected proxy. An access-denied message may mean the request reached the destination service. Keep a screenshot of the error page and the matching timestamp in the client logs; that’s more useful than simply reporting a “blank page.” One website failing doesn’t prove the entire route is down.

Compare the affected sites and browser environment first

Keep the route the same and visit different services to see whether everything fails or only one domain. If other sites work, check whether the affected site is undergoing maintenance, whether your account meets its region requirements and whether the URL is correct. Then try a private browsing window to rule out some extensions, cache and site data issues. Private browsing doesn’t change your exit route or replace a check of proxy routing.

If the issue only occurs in your current browser, check for a separate proxy extension, secure DNS or a managed browser policy. A browser may not use the system’s DNS settings, and an extension may override the system proxy. Note your current settings, then temporarily disable extensions you control to compare results. Don’t force changes to managed work policies. If another browser works, focus on the affected browser’s configuration instead of resetting the entire device’s network settings.

Use DNS lookup commands to observe what’s happening, not to jump to conclusions

On desktop, you can use the command below to look up a sample domain. It doesn’t contain account information, and you can substitute the domain where the issue occurs. Note whether the command returns a result or times out, and which DNS server it reports. Different regions or DNS services may return different addresses because of content delivery; that alone doesn’t mean something is wrong. The command output also doesn’t prove that your browser used the same DNS path.

nslookup example.com

If your system says the command isn’t available, don’t install unfamiliar tools just to troubleshoot. Use the system’s built-in network diagnostics or the client logs instead. When the client uses virtual IP mapping, system lookup results may differ from a regular direct connection. Check the client’s DNS documentation and connection logs; don’t mistake an internal mapping address for the website’s actual exit address or overwrite your settings with a DNS configuration copied from the internet.

Check whether DNS resolution and connections follow the same rules

The component that resolves a domain, the path used for the DNS request and the path used to connect to the site may differ. For example, the browser might resolve the name itself while the client routes the app’s connection, leading to a mismatch between the DNS result and the route’s exit. Start by restoring the client’s default DNS settings and confirming that its rules have loaded correctly, then reopen the app. Change one DNS option at a time and note how to undo it.

Don’t substitute a website’s IP address for its domain to test connectivity. Modern websites often rely on the domain name to select the site and validate its certificate, so visiting the IP directly can fail even when the network path works. Don’t disable certificate validation as a troubleshooting step, either. If an error mentions a system proxy port, check the local listening settings shown by your client instead of using a fixed port from an online guide.

SymptomCheck firstDon’t assume
Domain name won’t resolveDNS settings, browser secure DNS, loaded rulesThat every route is down
Connection timed outProxy routing, route path, destination responseThat DNS is necessarily the cause
Certificate errorSystem time, sign-in page, trusted networkDon’t ignore the warning and continue signing in
Only one site denies accessRegion, account status, site policyThat the whole internet is inaccessible

After checking, if several sites keep failing to resolve while DNS works on your direct connection, send support the error type, DNS mode, whether browser secure DNS is enabled and the relevant logs. Include only the log excerpts needed to identify the issue, and redact account and subscription details. Once access is restored, remove temporary test settings so they don’t leave behind confusing DNS rules when your network changes.

Slow speeds and peak-hour buffering: run comparable tests

First identify what’s slow: Does a webpage take a long time to open? Are downloads consistently slow? Does video keep buffering, or does audio break up during a live meeting? These symptoms can have different causes. Page loads are affected by DNS, images and scripts; downloads may be limited by the destination server; real-time services are more sensitive to changing latency and packet loss. One download test doesn’t represent the performance of an entire international route, and a connection-time figure in the client isn’t a transfer speed.

Rule out device and local network congestion first

Keep the destination service the same and check whether your device is syncing files, updating its system or uploading large files. Also check whether other devices on your local network are using a lot of bandwidth. A strong Wi-Fi signal doesn’t mean the connection is uncongested, and interference can occur even near the router. If possible, compare with a wired connection. If you can’t change how you connect, at least test from the same location to avoid mistaking changes in Wi-Fi quality for route performance.

Your device can affect the results, too. Too many browser tabs, a busy disk, overheating or power-saving mode can make pages sluggish and look like a network issue. Check system resource usage before comparing routes. For video, you can check the playback information provided by the platform, but don’t keep seeking to test different resolutions. Repeatedly seeking triggers buffering and makes it harder to judge playback stability.

Keep test conditions consistent when comparing routes

Use the same destination, device and network. Record how the current route performs, then try another route. Don’t change the download source at the same time. If your test tool lets you choose a server, use the same one; if it selects automatically, note any change in server location. Speed tests use subscription data, especially repeated large downloads. Check your remaining allowance in the dashboard before running more tests.

IEPL, relay and direct routes describe how traffic is routed; they aren’t a fixed speed ranking for every user. Your access network, the destination’s location and current routing conditions all affect performance. Compare route types within the same region first, then compare regions. If only one destination is slow, consider how its location matches the route’s exit region instead of assuming that the shortest geographic distance will be fastest.

For peak-hour slowdowns, look at the time and route together

If performance is normal during the day but slows in the evening, keep comparable records from both time periods. Check whether the same route repeatedly shows the issue and whether switching route types helps. If only your home connection slows down and the same device works on another trusted network, investigate the local network or ISP route. If similar issues occur on the same route across different networks, send your records to support for a route-side check.

“Stable even at peak times” is a service consideration, not a guarantee of availability on every network or for every destination. Streaming platforms may change content delivery during busy periods, and download sites may limit speeds. When reporting an issue, say whether it affected browsing, downloads, video or calls, and what happened after you switched routes. “This service buffered repeatedly, but worked on another route” is more useful than “everything is slow at night.”

Subscription data limits and current transfer speeds are separate things. Monthly plans cost ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. These figures describe plan prices and data allowances, not different guaranteed speeds. If you’re running out of data, see plan pricing. If you have data remaining but transfers are slow, keep investigating the route rather than assuming that upgrading will fix it.

For regular work, keep a backup route that you’ve tested with your intended service, and check that it works before an important meeting or long transfer. Avoid switching exits repeatedly during a task, as your existing session may drop. If peak-hour performance repeatedly degrades, stop running the same speed test over and over. Keep your comparison results and submit a ticket so the investigation can focus on a specific route.

Frequent disconnections and mobile background drops

Distinguish between the client actually stopping, the network tunnel dropping and an app session expiring. If the client still shows connected and other sites work, but a meeting or download stops, the issue may be with the app or destination service. Note what the device was doing just before the disconnection: locking, switching networks, closing a laptop, entering power-saving mode or staying on the same network. The action that triggers the issue is often more useful than the screen shown afterward.

Check network switching and recovery from sleep

When a device switches from Wi-Fi to mobile data or moves between wireless access points, its network address may change and existing sessions may not survive. Wait for the system to confirm that the new network is available, check whether the client reconnects, then retry the request. If the issue only occurs after switching networks, focus on automatic reconnection and network permissions rather than treating it as a random drop during stationary use.

After a computer wakes from sleep, the network interface, proxy settings and app connections may recover in a different order. First confirm that regular network access is back, then check the client’s status. Download tools and remote-work apps may still be holding sessions from before sleep; restart the task after the connection is restored. Don’t keep clicking Connect before the network is ready. That can clutter the logs with repeated starts and stops, making the original issue harder to find.

On mobile, check background activity restrictions

On Android, check whether background activity, battery optimization or background data limits are affecting the client. Settings names vary by manufacturer, so look in the app information and battery settings. Note the original settings before changing anything, and make only the changes needed for the client to stay connected. Disabling all power-saving features isn’t recommended for troubleshooting. Keeping an app in the recent apps list doesn’t necessarily allow it to keep running.

On iOS, check that the system’s connection configuration is still enabled and that no other network configuration is taking over. If one app stops transferring data when the screen locks, that may be due to its own background execution rules, not a VPN disconnection. After unlocking, check connectivity in a browser and then check the client status. If the client is still connected but the app needs to reload, record the app behavior separately from the network status.

PlatformCheck firstImportant limits
WindowsWake from sleep, system proxy, background processesDon’t remove managed network policies without approval
macOSNetwork recovery, connection permissions, other network toolsConfirm network access is restored before reconnecting
AndroidBattery optimization, background data, app restrictionsSetting names vary by device
iOSSystem connection settings, connectivity before and after lockingDistinguish an app pausing from a connection dropping
LinuxProcess status, network management, routing after sleepSave the original configuration before making changes

If disconnections happen during active use, check the route next

If the device isn’t locked, asleep or switching networks but the connection still drops, compare routes while keeping the destination service the same. If it happens on only one route, note its name and keep the disconnection logs. If it happens on every route, check local Wi-Fi quality, network filtering tools and whether the client process has stopped. If the logs repeatedly show that the process was terminated, investigate system restrictions or software conflicts instead of changing settings for the destination website.

After reconnecting, check that the task you were doing has resumed. A file upload may not be complete, and an online document may still be waiting to sync. Don’t close the app just because the connection icon is back. Before important work, check the device’s battery and network conditions, and keep the app’s resume or draft features enabled. If a specific action consistently triggers a disconnection, include it in your support ticket so the issue can be reproduced rather than treated as an isolated error.

Subscription update failed: check the source and account status

A subscription update gives the client the route configurations currently available to you. It’s separate from whether a particular route connects successfully. An update failure doesn’t necessarily invalidate routes already imported, and working routes don’t prove that the subscription URL is still valid. Check whether the client reports a download failure, a permission error, an unrecognized format or an empty list after updating. Keep the exact error, then decide whether to check the network, account or import method. Don’t delete your existing configuration right away.

Recheck the subscription link in the dashboard

Use the dashboard overview to check your account and subscription status, and make sure you’re using the intended account. VPN40 doesn’t require an email address; you can create an account with a username and password. Keep your username somewhere safe. Signing in to different accounts on different devices can make differences in plan status look like a client issue. A browser’s saved sign-in state doesn’t confirm that you’ve checked which account you’re using.

Copy the subscription information again using the link in the dashboard. Don’t piece it together from an old chat or screenshot. Check that the copied text doesn’t include spaces, line breaks or other notes. If the dashboard provides an import option for your client, use it instead of sending a configuration format to a parser that doesn’t support it. If your list changes after an update, compare it with the dashboard before trying to convert it with an external tool.

Choose the next check based on the error

For a request timeout, first check whether the dashboard opens and whether the client needs the current proxy to update the subscription. In some environments, subscription updates and web browsing use different paths, so the browser may work while the client can’t fetch the subscription. Check the client’s update settings and logs, and retry on a trusted network if needed. Don’t change both the proxy mode and subscription URL at once without a backup.

For a format error, check whether the copied content is actually a sign-in page, error message or other webpage. The client may report a parsing error if it expected a configuration but received a webpage instead. Don’t post the entire response publicly; it may contain account information. Share only the error type and any necessary redacted excerpt with support so they can confirm the right import format.

For a permissions or account-status message, check the dashboard to see whether your plan is active, whether data remains and whether your order is complete. Monthly subscription data resets each month on the activation date; don’t estimate it by calendar month. Data packs don’t expire and remain available until used. “Doesn’t expire” describes the validity rule; it doesn’t mean you can keep transferring after the allowance is used up. For current prices and rules, see the plans page instead of relying on an old cache.

After a successful update, confirm the new configuration is active

A client may store several configuration files. A subscription update can succeed while the client continues to use an older file. Check which configuration is enabled, when it was last updated and which route is selected, then retry the request. If route names have changed, an old pinned selection or app-specific rule may no longer point to the right item. Check those settings to make sure the updated list still provides an available route for your request.

Before importing again, note the configuration name and any local rules you need, and make sure you can restore them before removing a damaged entry. Don’t delete the client’s entire data folder as a routine step; it may contain custom rules and useful diagnostic information. Get the client through the dashboard download page. Sign in to access your subscription; iOS access depends on the permissions shown in the dashboard.

If you think your subscription information has been exposed, first check whether the dashboard provides a reset or management option, and confirm what to do through a support ticket. Changing your sign-in password and invalidating an old subscription aren’t necessarily the same operation. After taking action, update the affected devices with valid configurations and test each one. Otherwise, update failures on old devices may be mistaken for a new route issue.

One app can’t connect: check proxy routing and rules

If your browser works but one app doesn’t, check whether the app’s requests are reaching the client before assuming the route is down. Apps may use the system proxy, configure their own proxy or connect directly. Seeing the system proxy enabled on desktop doesn’t mean every process uses it. Compare the browser and affected app on the same route, and note whether the issue occurs during sign-in, content loading, file transfers or a live call.

First check whether the app’s requests reach the client

If the client supports connection logs, open the app, perform a specific action and check whether a matching request appears at that time. An app may connect to several domains, so don’t guess which requests belong to it based on a name alone or mistake background traffic from another process for the app’s activity. If no relevant request appears, check the app’s proxy settings and the client’s routing mode first. If a request appears but fails, check which rule and exit route it matched.

A system proxy generally relies on apps following the system’s settings. A virtual network interface can cover a broader range of system traffic, with different permissions and effects. Check your client’s documentation for supported modes and how to enable them. Don’t change system routes or install an unknown network driver just to make one app work. For managed work apps, check your organization’s requirements to avoid conflicts with corporate network policies.

Compare rule-based routing with a temporary test mode

On a device you’re allowed to configure, use a temporary comparison mode provided by the client to find out whether routing rules are causing the issue. Note the original mode before switching, and restore it when you’re done. If the test mode works but rule-based mode doesn’t, check whether the app’s domains are incorrectly set to bypass the proxy or use a different exit. If neither mode works, check the app account, destination service and route region instead of adding more rules.

Keep new rules limited to the confirmed destination whenever possible, and check their priority. Overly broad domain suffixes or process rules can affect other services and disrupt syncing, payments or local network access. Apps that use a browser for sign-in may also pass a session between the browser and app. If they use different exits, sign-in may loop back to the start. Check the complete sign-in flow, not just the final page.

Separate protocol, region and service-access issues

If text chat works but calls fail, or web content loads but real-time features don’t, the app may use different transport methods for each feature. A working browser page doesn’t rule out a routing problem, but it’s not a reason to change transport settings at random. Check the app’s error message and client logs for protocol details, then include the affected feature, route and steps to reproduce in your support ticket so support can confirm what your current configuration supports.

Streaming services and AI tools are also subject to platform region policies, account eligibility and exit IP recognition. A working network connection doesn’t mean every feature or piece of content will be available. If you see a region notice, check whether the route region matches the platform’s account requirements. Changing your exit route doesn’t change your account region. See our streaming access guide and AI tools guide. Platform access restrictions aren’t general network outages.

If the app is still using an old connection, you may need to fully quit and reopen it after changing rules. Save drafts and active tasks first. Desktop apps may keep running in the background after you close a window, so check their process status. For security-sensitive accounts, don’t repeatedly sign in while switching between multiple exits to test; the platform may ask for additional verification. A repeatable, low-impact page load is a better test.

If the request reaches the client, the route works in your browser, but a particular feature still fails consistently, stop making general changes. When contacting support, include the app name, operating system, failing step and comparison tests you’ve already completed. If needed, also contact the destination platform to check account or service restrictions. Network providers and app platforms have different responsibilities, so identifying which one applies can save time.

Device limits and account alerts: identify the source first

VPN40 has no limit on the number of devices connected at the same time. If you see a “device limit” or “too many connections” message, don’t assume you need a higher-tier plan. First check whether the message comes from the VPN40 dashboard, the client or the service you’re trying to access. Streaming platforms, work apps and other services may each limit signed-in devices or active sessions. Those policies are separate from VPN40’s simultaneous-device policy and should be checked individually.

Identify where the message comes from

Keep the message and the screen where it appeared, and note whether it showed up before connecting, during connection or after signing in to the destination service. If the client connects normally but one platform reports a device limit, check device or session management in that platform’s account settings. If the message appears while importing a subscription, check the import method and configuration source instead of immediately removing all devices. If the source isn’t clear, send support a screenshot with sensitive details redacted.

A device may be running several related components, such as a background service, desktop interface and old client process. Duplicate processes can cause port conflicts or connection issues; that doesn’t mean this service is limiting simultaneous devices. Check for duplicate processes, then close only the ones you don’t need. Don’t terminate system networking processes you can’t identify. If an issue occurs on a managed device, ask your administrator to check the installation and how it’s running.

Check the account, plan and data allowance instead of guessing

Check your username and plan status in the account overview, then compare them with the account signed in on your other devices. Shared browsers, device changes or password manager autofill can sign you in to a different account. Confirm the account before checking orders, so you don’t mistake “no plan on this account” for a missing purchase. Don’t send your password to support to prove your identity; provide only what the dashboard’s ticket form requests.

Monthly subscription data resets on the activation date each month. If you upgrade mid-cycle, the price difference is prorated based on the remaining days. If you’re unsure about the reset date or status after an upgrade, check the dashboard record and ask support to verify it. Don’t rely on calendar months or your own calculations. Data packs cost ¥158 for 300GB, ¥358 for 1000GB and ¥658 for 3000GB. They remain available until used and never expire. See the plans page for full billing details.

Check payment and account status separately

Payment methods include Alipay / WeChat Pay / USDT. If the payment page says the transaction is complete but your order status hasn’t updated in the dashboard, check the existing order first. Don’t create another order or pay again. Keep the order reference, payment method and a screenshot of the status, and ask for a check through a dashboard support ticket. Redact personal and financial details unrelated to the issue from payment records, and don’t post them publicly.

If your plan looks correct in the dashboard but the client still shows an old status, you may need to update the subscription or reload the current configuration using the client’s own controls. First confirm the subscription update succeeded, then test the connection. Signing out of the dashboard doesn’t necessarily make the client update automatically. The dashboard’s web status, the client’s cache and its active configuration are separate layers; checking each one is more useful than repeatedly signing out.

Account security also affects a reliable experience. If someone else gets your subscription information, you may notice unexpected data usage. Don’t assume a change in usage proves your account was exposed; also consider system updates, cloud syncing and speed tests. Compare usage across devices, pause unnecessary transfers, then check through the dashboard support channel. If you need to reset anything, confirm how to move your other devices first so that security steps don’t create new connection issues.

If you ultimately need a refund, VPN40 offers a 7-day no-questions-asked refund. See the Terms of Service for details. Troubleshooting shouldn’t mean endless attempts to change settings. For billing, order or server-side access issues, provide the relevant details and ask support to check them; you don’t need to buy another plan to prove the problem exists.

Support ticket details and recovery checks: keep a reproducible record

Consider submitting a support ticket if your direct connection works but routes in different regions keep failing; a subscription still returns the same error after you fetch it again from the dashboard; the order and plan status don’t match; one route repeatedly fails under the same conditions; or a system permission or client error can’t be resolved through the interface. Support needs a clear symptom and repeatable steps, not a list of complicated settings you’ve tried. Clear details reduce back-and-forth.

Describe what happened, not just your conclusion

Start with how things normally worked, then explain what changed and how to reproduce the issue now. For example, an app failing to reconnect after the device is unlocked while the browser still works is different from every request being disconnected. Include the operating system, the name shown in the client, network type, selected route and destination service. Get client details from the app itself; don’t guess based on the installer’s filename or another guide.

Give the most accurate time you can and say whether automatic time sync is enabled. Use the route name exactly as the client displays it; “Japan route” alone may not identify which one you used. Say whether the issue affects every website, a specific platform or just one feature, and what happened after changing the route, network or browser. Be clear about tests you couldn’t run. Don’t change a work network just to complete a comparison for a ticket.

Share only the necessary log excerpts, and check for sensitive data first

Use the client’s log viewer or export option, and include only the entries relevant to the time of the issue. Full logs may contain subscription URLs, account identifiers, requested domains or device information. Review and redact unrelated details before sending them. Don’t paste an entire configuration file into a ticket; it may contain connection credentials. Check screenshots for address bars, QR codes and dashboard pages, too. A subscription QR code may contain sensitive information.

VPN40’s privacy messaging is that it keeps no logs. That doesn’t mean the local client won’t display connection information for diagnostics. Local diagnostic records and the service’s policies are separate matters; see the Privacy Policy for details. Share only what’s needed to resolve the issue. You don’t need to disclose your browsing history to demonstrate a route problem.

Organize your ticket with a clear structure

In your ticket, list: device and operating system; client in use; network type; affected route; destination service and feature; exact error; steps to reproduce; tests already completed; and what you’d like support to check. Use a short, complete sentence for each item. If the same account has both an order issue and a connection issue, describe them separately. Don’t attach payment records and network logs without explaining which issue they relate to.

If support asks you to run more tests, first check what each step changes and how to restore your settings. Before changing proxy mode, DNS settings or a configuration file, note the current state. Report one clear result at a time, such as “the website worked after switching routes without changing networks,” rather than “it works now” after making several changes. If a test could interrupt a meeting or upload, save your work and choose a suitable time.

After recovery, revert temporary settings and test the complete workflow

Getting a webpage to load is only the first recovery check. Confirm that the original app feature works again, the subscription updates successfully, and the device behaves as expected after sleep or a network switch. Restore temporary proxy modes, browser extension changes and DNS settings one by one using your notes. If you need to keep a setting, record why. Don’t leave behind overlapping configurations that will make the next issue harder to diagnose.

Finish by keeping a short record for your own reference: the configuration you normally use, backup routes you’ve tested, past errors and the steps that resolved them. Use Quick Start for initial setup, the route list for route information and plan pricing for billing rules. Keeping these details separate helps distinguish network issues from platform access and account status, and makes it easier to explain what changed if you contact support again.

First Month Free