Choose how users connect
Use an Anycast endpoint for a single global entry point, or choose individual regions for more control over where users enter the network.
LuckVM Global Network Accelerator LGA
Keep your origin. Extend your reach.
Global network acceleration
A better path to your applications
Connect distributed users to your APIs, remote desktops and TCP/UDP services through a managed acceleration endpoint. Keep your existing public origin, choose a routing model and manage listeners, TLS and outbound usage in one place.
Keep your deploymentPublic IP or hostname origins
Choose your routingAnycast or regional endpoints
Understand your usageMonthly outbound transfer
LUCKVM NETWORKConnection path illustration
Application usersRemote teamsAPI clients
GLOBAL ACCELERATIONLuckVMStandard / custom routing
Your existing originPublic IP or hostname Β· Service port
Endpoint β Accelerated path β Origin
BUILT FOR CONNECTIONS
Built around your application
Not just static content
Global acceleration is designed for connections that must reach an origin: dynamic requests, database sessions and interactive remote access. It complements your deployment without requiring a server migration.
Work with existing services
Configure listener and origin ports for TCP/UDP workloads. Use TCP passthrough for origin-side TLS, or bind a certificate for an HTTPS listener.
Keep control after deployment
Review endpoint addresses, deployment status and outbound usage. Update primary and backup origins, listeners and health checks in the customer portal.
TWO WAYS TO CONNECT
One global endpoint or regional control
Choose according to user distribution, required access regions and the IP allowance included in your plan.
A single Anycast entry point
Use an Anycast IP for global access without selecting regions individually. Availability depends on your origin and plan.
- Uses one acceleration IP
- No manual acceleration-region selection
- A straightforward starting point for distributed users
Select regional acceleration endpoints
Use intelligent DNS and dedicated regional IPs to direct traffic into selected regions. Optional Mainland China acceleration makes eligible CN2 routes available.
- Each selected region uses one acceleration IP
- Region count is limited by your plan
- Mainland China has separate plan and overage pricing
CHOOSE YOUR WORKLOAD
Built for connections that cannot wait for a cache
Choose a preset, then adapt the listener ports and routing to your actual workload.
Database access
Connect applications and database clients across regions with TCP listeners for services such as MySQL and PostgreSQL.
TCP Β· Database clientsRemote Desktop & SSH
Configure SSH and RDP access for distributed operations teams. Remove unused preset ports and retain your normal access controls.
SSH Β· RDP Β· Remote administrationCDN integration & HTTPS
Add an acceleration path to an existing domain-based architecture. Choose TLS passthrough or a certificate-bound HTTPS listener and avoid origin loops.
Hostname endpoints Β· TLSCustom TCP/UDP services
Configure ports and routing for APIs, interactive applications and other services that need to reach a live origin.
TCP / UDP Β· Custom listenersPLANS FOR YOUR BUSINESS
Choose a plan for your workload
Compare included outbound transfer, acceleration IPs, concurrent connections and overage rates. Select the subscription term when you configure your service.
Monthly transfer allowanceVisible overage ratesFlexible subscription terms
Plans & pricing
Choose a plan β Configure β CheckoutMatch the allowance and connection limits to your expected workload.
Loading available plansβ¦
The checkout page shows the final amount. Outbound allowance resets monthly; Mainland China and other routes have separate overage rates.
FROM PLAN TO CONNECTION
From plan to production traffic
Prepare a reachable origin, its service ports and DNS access if you use a hostname endpoint.
- Choose a plan
Sign in and select the allowance and optional Mainland China access you need.
- Configure the service
Choose the term, origin region, routing and listener-to-origin port mappings.
- Wait for deployment
Open your instance in the customer portal and confirm the deployment status.
- Connect and test
Use the acceleration IP or set your CNAME record. Test from real user networks.
Before you switch traffic
Allow the required origin ports and test end-to-end connectivity. A hostname endpoint must differ from its origin hostname. For HTTPS, install the certificate on the origin for TCP passthrough or upload it in the portal for TLS termination.
FIND THE RIGHT FIT
Global acceleration or a CDN?
Choose for your traffic pattern. The two can also be used together when the request path is configured correctly.
| Requirement | LuckVM LGA | CDN |
|---|---|---|
| Primary focus | Connection and transport paths to an origin | Caching and edge content delivery |
| Typical workloads | Dynamic APIs, remote access, TCP/UDP services | Cacheable images, scripts and downloads |
| Configuration | Origin, routing and listeners | Hostname, cache policy and origin settings |
| Using both | Validate the complete request path and avoid circular origin references. | |
BEFORE YOU START
Questions before you deploy
Clear answers about billing, Mainland China access, TLS and what acceleration can realistically improve.
Does LGA replace my servers or CDN?
No server migration is normally required: LGA connects users to your existing public origin. It optimizes the connection path rather than providing application hosting or a general-purpose content cache. A CDN remains useful for cacheable assets; validate the request path before combining the two.
Is Mainland China access included in every plan?
No. Enable Mainland China acceleration when comparing or configuring plans, then choose custom routing and an available CN2 region. Standard Anycast routing does not by itself select a CN2 route. The Mainland China option has its own price and outbound overage rate.
What counts toward transfer, and when does it reset?
Only outbound traffic from the acceleration network to users is counted; inbound traffic is not charged. The allowance resets on the monthly anniversary of activation, using Asia/Shanghai time, rather than every 30 days. If the anniversary date does not exist in a month, the boundary falls on that monthβs last day.
What happens when my allowance or account balance runs out?
With outbound overage balance billing enabled, usage beyond the allowance is charged at your planβs rate. A detected balance of zero or less triggers suspension. Without balance billing, exhausting the allowance triggers suspension. Metering and shutdown take time; additional usage is still chargeable and may make the balance negative.
Can I keep my existing HTTPS certificate?
For TCP 443 passthrough, keep the certificate on your origin. To terminate TLS at the acceleration edge, use a hostname accelerator and upload its matching PEM certificate chain and private key in the customer portal. After binding finishes deploying, configure the HTTPS listener and origin protocol.
How many regions can I select?
Standard routing uses one acceleration IP. With custom routing, each selected region uses an acceleration IP and the maximum number is set by your plan. Available and disabled regions depend on the origin and Mainland China option; use the live configuration list.
What latency reduction can I expect?
There is no universal latency reduction percentage. Results depend on user networks, origin location, routing, protocol and server performance. Compare direct and accelerated connections from representative user networks before moving production traffic.
What should I do if provisioning fails?
Check the instance status in the customer portal and contact support with the instance details. Do not place a duplicate order just to retry provisioning. Deployment is asynchronous, so a submitted request is not proof that the endpoint is ready.
Ready to connect a distributed audience?
Choose a plan, or discuss your origin and user regions with our team.