Cloudflare-generated 1xxx error responses now include a standard Retry-After HTTP header when the error is retryable. Agents and HTTP clients can read the recommended wait time from response headers alone — no body parsing required. Changes Seven retryable error codes now emit Retry-After:
Error codeRetry-After (seconds)Error name1004120DNS resolution error1005120Banned zone101530Rate limited1033120Argo Tunnel error103860HTTP headers limit exceeded120060Cache connection limit12055Too many redirects The header value matches the existing retry_after body field in JSON and Markdown responses. If a WAF rate limiting rule has already set a dynamic Retry-After value on the response, that value takes precedence. Availability Available for all zones on all plans. Verify Check for the header on any retryable error: curl -s --compressed -D - -o /dev/null -H "Accept: application/json" -A "TestAgent/1.0" -H "Accept-Encoding: gzip, deflate" "/cdn-cgi/error/1015" | grep -i retry-after References:
RFC 9110 section 10.2.3 - Retry-After Cloudflare 1xxx error documentation
Fetched April 4, 2026