HTTP 507 — Insufficient Storage
5xx Server Error
What it means
The server cannot store the representation needed to complete the request.
What to do about it
Check disk space. A full disk also causes surprising 500s elsewhere, since logs and temp files stop writing.
Where it sits
507 belongs to the 5xx family: The server failed to fulfil an apparently valid request. The fix is on the server side.
HTTP/1.1 507 Insufficient StorageChecking it yourself
# see the status code and headers only
curl -sI https://example.com/path
# follow redirects and print each hop
curl -sIL -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com/path
# JavaScript
const r = await fetch(url);
console.log(r.status, r.statusText);How this code behaves
| Cacheable by default | No — caches must not store this response unless explicit cache headers permit it. |
| Safe to retry | Yes, with backoff. This is a transient condition; retrying the same request is reasonable. |
| Effect on search indexing | Repeated server errors reduce crawl rate and eventually drop pages from the index. |
Returning 507 correctly
# nginx
return 507;
# Express
res.status(507).json({ error: 'Insufficient Storage' });
# Go
w.WriteHeader(507)
# Python (Flask)
return jsonify(error='Insufficient Storage'), 507;Frequently asked questions
What does HTTP 507 mean?
The server cannot store the representation needed to complete the request.
How do I fix a 507 error?
Check disk space. A full disk also causes surprising 500s elsewhere, since logs and temp files stop writing.
Is 507 a client or server problem?
A server problem. The request was valid; the server failed to fulfil it. Nothing the client changes will help.