< HTTP/1.1 509 Bandwidth Limit Exceeded509 Bandwidth Limit Exceeded (cPanel Hosting)
cPanel documents 509 Bandwidth Limit Exceeded for an administrator-imposed transfer limit. Confirm account usage in WHM and adjust the quota or wait.
- Cacheable
- Only with explicit freshness
- Retry?
- After the hosting quota resets or the administrator adjusts it
- Usually sent by
- cPanel hosting
TL;DR: cPanel documents 509 Bandwidth Limit Exceeded when a hosting server reaches an administrator-imposed bandwidth limit. Check the account’s usage and quota with the host. Wait for the next cycle or have the administrator adjust the limit.
What it means
509 is non-standard. cPanel’s error-code reference documents the label “Bandwidth Limit Exceeded” and tells users to wait for the limit to reset or contact the system administrator.
Here, “bandwidth” refers to a hosting transfer allowance. WHM’s Limit Bandwidth Usage interface manages monthly account limits. Do not infer a broken network link or a requests-per-second limit from the word “bandwidth”.
The verified scope is cPanel hosting. This is not a standard Apache HTTP status with a universal module, directive or quota value. Diagnose the hosting account before adding speculative Apache configuration.
Confirm the limit
Check the actual status and body from the affected URL. This read-only command uses an example hostname; replace it with the failing site:
curl -i https://example.com/An error page headed “Bandwidth Limit Exceeded” is useful evidence, but record the HTTP status too. Send the hosting administrator the affected hostname, timestamp and status, and ask them to confirm the account’s current transfer usage and enforced limit.
In WHM, inspect Account Functions → Limit Bandwidth Usage for the account. Compare the account selected in WHM with the account that owns the failing domain. Do not increase an unrelated account’s quota because its name looks similar.
Restore service
If the limit was intentional, decide whether to wait for its reset or buy enough transfer allowance for the remaining cycle. If you administer the server, adjust the account’s limit in WHM after checking usage. For already limited accounts, cPanel also documents Account Functions → Unsuspend Bandwidth Exceeders to remove bandwidth restrictions.
Review the traffic that consumed the allowance before setting a larger quota. Investigate unexpected downloads, repeated asset requests or automated traffic using your own logs. Those are possible investigations, not causes established by status 509 alone.
After the account change, repeat the request to the original URL and verify the host’s usage figures. Record the limit change and the next review point so that the same surprise does not recur without an owner.
Distinguish it from other limits
429 describes request rate limiting. 503 describes temporary inability to serve requests. Neither defines this hosting account’s transfer allowance, and retrying immediately does not change the quota.
Related
Frequently asked questions
Is 509 a standard HTTP status code?
No. cPanel documents 509 Bandwidth Limit Exceeded for reaching a bandwidth limit imposed by the system administrator.
How do I fix a cPanel bandwidth limit error?
Ask the hosting administrator to check account usage and its limit in WHM. The administrator can adjust the quota, or you can wait until the limit resets in the next cycle.
Does 509 mean Apache itself defines a bandwidth quota?
This page documents cPanel hosting behavior. It does not establish a universal Apache limit, module configuration or default bandwidth allowance.
Sources
Related
HTTP 503 Service Unavailable: Causes, Fixes and Retry-After
Fix HTTP 503 Service Unavailable: nginx no live upstreams, Kubernetes endpoints, ALB healthy hosts, Cloudflare, and a maintenance page with Retry-After.
HTTP 429 Too Many Requests: Causes, Retry-After and Fixes
Fix HTTP 429 Too Many Requests: read Retry-After and RateLimit headers, back off with jitter, and set up express-rate-limit v7, nginx limit_req and Cloudflare.
529 Site Is Overloaded (SSL Labs and Anthropic)
529 is a non-standard overload code used by SSL Labs and Anthropic. Identify the API, inspect overloaded_error, and back off without confusing it with 429.
561 Unauthorized (AWS ALB Authentication)
AWS ALB 561 means the identity provider returned an error during listener authentication. Read error_reason in access logs and inspect the IdP response.