Site Is Frozen
ActiveHTTP 530 is used by Cloudflare Pages and Pantheon to indicate a site has been frozen due to inactivity (Cloudflare Pages) or the origin returned an unexpected 1xxx status code (Cloudflare edge). The most common 530 scenario is a Cloudflare Pages site that has been suspended due to being over the free tier limits or inactivity on paid plans.
Description
530 has two distinct uses in Cloudflare's ecosystem. Cloudflare Pages returns 530 when a project has been frozen – this happens to sites over free tier limits or inactive paid projects. The second use is Cloudflare's edge returning 530 when the origin server sends a 1xx informational status that Cloudflare doesn't support forwarding (since 1xx codes are hop-by-hop). Pantheon hosting also uses 530 for 'Site Frozen' when a site is suspended. Unlike 521–526 which indicate origin server problems, 530 often indicates account/billing status.
Examples
HTTP/1.1 530 Server: cloudflare
# Cause: Cloudflare Pages project frozen due to inactivity or over limits
# Fix: Log into Cloudflare dashboard → Pages → Unfreeze project# Origin server sends HTTP/1.1 100 Continue unexpectedly
# Cloudflare cannot forward 1xx to the client
# Cloudflare returns 530 instead
# Fix: Ensure origin doesn't send 1xx responses that Cloudflare should pass throughEdge Cases
- •530 from Cloudflare Pages is a billing/account issue, not a server error – check the Cloudflare dashboard.
- •Pantheon's 530 is triggered when a site environment is suspended and requires reactivation in the Pantheon dashboard.
- •Unlike other Cloudflare 5xx errors, 530 may not include a CF-RAY header if the request never reached Cloudflare's edge processing.
- •The status line for 530 from Cloudflare is just '530' with no reason phrase – this is non-standard.
When You'll See This
- →Cloudflare Pages project frozen due to inactivity
- →Cloudflare Pages project over free tier build/bandwidth limits
- →Pantheon hosting site suspended
- →Origin server sending unexpected 1xx status that Cloudflare blocks
Implementation References
| Language | Constant |
|---|---|
| Go | 530 (no standard constant – Cloudflare/Pantheon proprietary) |
| Node.js | 530 (not in http.STATUS_CODES) |
| Python | response.status_code == 530 |
History
530 was adopted by Cloudflare Pages and Pantheon independently for site suspension scenarios. It is not part of the original Cloudflare 520–527 error range but has emerged as a de-facto additional code in the Cloudflare ecosystem.
Related Status Codes
Related Headers
FAQ
How do I fix a 530 error on my Cloudflare Pages site?
Log in to the Cloudflare dashboard, navigate to Workers & Pages, find the affected project, and look for a freeze or suspension notice. Free tier projects can be unfrozen manually. If you are over usage limits, you may need to upgrade to a paid plan or reduce usage.
Is 530 the same as 503 Service Unavailable?
No. 503 is a standard HTTP status indicating the server is temporarily unable to handle requests, with an expected recovery. 530 is Cloudflare/Pantheon-specific and indicates an account-level suspension – the site is administratively frozen, not temporarily overloaded. 530 requires dashboard action to resolve, not just waiting.