GA has three categories of quotas. Some can be raised on request; the rest are fixed product limits.
General quotas: cap the cloud resources a single Alibaba Cloud account can use.
API rate quotas: cap how frequently the account can call the GA OpenAPI.
Entitlement quotas: grant the right to use a feature after Alibaba Cloud authorizes it — a default of 0 means the feature is not enabled.
The defaults listed on this page are for reference only. The value shown in the Quota Center is authoritative.
Limits
Configuration | Standard | Basic |
Supported acceleration areas | ||
Acceleration IP types |
| Elastic IP only |
Acceleration IPs per instance |
| Controlled by |
Minimum bandwidth per acceleration region |
| EIP: 2 Mbps |
Supported backend types |
| ENI/CLB/NLB/ECS |
Routing types | Intelligent routing, custom routing | N/A — acceleration IP maps directly to endpoint |
Listener port range | 1–65499 | N/A |
Ports per listener |
For TCP/UDP listeners on a pay-as-you-go instance, the total ports and port ranges across all listeners on one instance is also capped by | N/A |
TCP/UDP fragmented packets | Not supported | Not supported |
GA runs on a distributed high-availability cluster. Per-connection throughput is bounded by the single-core performance of one data-plane node, while the bandwidth cap you configure is spread across multiple servers in the cluster. If your workload is dominated by high-throughput, long-lived connections, a single connection may not reach the instance's peak bandwidth. Split traffic into multiple concurrent connections to use the full bandwidth capacity.
General quotas
Adjustable quotas
Quota name | Description | Default | Maximum |
| Maximum number of GA instances per user | 10 | 40 |
| Forwarding rules per listener | 20 | 150 |
| Total forwarding condition entries per listener | 40 | 150 |
| Virtual endpoint groups per listener | 10 | 150 |
| Maximum endpoints per endpoint group | 4 | 30 |
| HTTP(S) connection idle timeout for pay-as-you-go Standard instances | 60s | 600s |
| HTTP(S) connection request timeout for pay-as-you-go Standard instances | 180s | 600s |
| Acceleration IPs per Basic instance | 20 | 200 |
Non-adjustable quotas
Quota name | Description | Default |
| Maximum listeners per accelerator instance | 50 |
| Endpoint groups per listener | 10 |
| Maximum ports per listener | 30 |
| Maximum extended certificates per HTTPS listener | 25 |
| Origin probes per GA instance | 5 |
| Idle acceleration IPs per Basic instance | 10 |
| Endpoints per Basic instance | 200 |
gaplus_quota_listener_per_accelerator cannot be raised through the Quota Center. Contact your account manager to request an increase.API rate quotas
API rate quotas cap how frequently a single Alibaba Cloud account can call the GA OpenAPI. The console displays the value as calls per 60 seconds — 300/60(s) means up to 300 calls every 60 seconds. To look up the limit for each operation, use either entry point:
The API rate quota list page in the Quota Center.
The API Rate Quotas tab on the Quota management page in the Global Accelerator console.
Most operations are capped globally; a few are unitized and counted per region. API rate quotas can also be raised from the Quota Center. An approved increase takes effect in about 3 minutes.
Entitlement quotas
Entitlement quotas require authorization from Alibaba Cloud before use. GA offers two:
Console downgrade
ga_whitelist/instance_downgrade: allows downgrading the specification and bandwidth plan of a Standard instance.Acceleration region allowlist
ga_whitelist/region_whitelist: makes hidden acceleration regions visible and usable.
View and raise quotas
Manage quotas from the Alibaba Cloud Quota Center or from the Global Accelerator console quota management page. Both entry points expose the same set of quotas.
By default, only the Alibaba Cloud account (root account) can operate the Quota Center. RAM users must first be granted the
AliyunQuotasFullAccesspermission.Each cloud product's technical support team reviews quota increase requests. A reasonable target value and a thorough justification improve the odds of approval. Results are delivered by SMS and email.
In resource directory scenarios, create a quota template to automatically submit increase requests for new member accounts as they join the resource directory. Templates require sign-in with the enterprise management account and an enabled resource directory.
Console
Sign in to the Quota management page, pick a quota category, and locate the target quota.
View a quota: review the name, description, and current usage of the quota.
Raise a quota: click Apply in the Actions column, fill in the desired value and justification, then submit. Track the review status under Application History — a status of Approved means the increase is live.
API
ListProductQuotas: list GA general quotas and their usage.
GetProductQuota: get details and usage for a specific quota.
CreateQuotaApplication: submit an increase request, specifying the quota, desired value, and justification.
ListQuotaApplications: check the review status of your applications.
To cross-check actual GA resource usage, call GA resource-listing APIs such as ListAccelerators, ListListeners, and ListEndpointGroups.