HTTP 507 — Insufficient Storage
HTTP 507
Insufficient Storage
The server cannot store what the request needs it to store — it is out of space or over quota.
What 507 actually means
A WebDAV code that has been widely borrowed for any storage-exhaustion failure. The request was valid and would have succeeded, but the server has nowhere to put the result: the disk is full, the account is over its quota, or the storage backend rejected the write. Unlike most 5xx codes it has a clear and mundane fix, and the fix belongs to whoever runs the server.
Common causes
- The server's disk or volume is full
- A per-user or per-account storage quota exceeded
- A database or object storage backend out of space
- Log files or temporary files filling the partition
- Inodes exhausted even though free bytes remain
If you're just trying to view the page
- Free up space in your account if the service shows a quota — delete old files or empty the trash
- If it is not your quota, wait and report it; the operator has to add space
If it's your site
- Check free space with `df -h`, and free inodes with `df -i` — an inode-exhausted filesystem reports space available but cannot create files
- Look for runaway logs, orphaned temp files and old backups before expanding the volume
- Add monitoring and alerting on disk usage at a threshold that leaves time to act
- Return a clear message distinguishing "your quota" from "our disk"; they are very different for the user
Reference
- Status code
- 507
- Reason phrase
- Insufficient Storage
- Category
- 5xx — Server Error
- Cacheable by default
- No
- Defined in
- RFC 4918 §11.5
Common questions
- What does HTTP 507 mean?
- The server cannot store what the request needs it to store — it is out of space or over quota. A WebDAV code that has been widely borrowed for any storage-exhaustion failure. The request was valid and would have succeeded, but the server has nowhere to put the result: the disk is full, the account is over its quota, or the storage backend rejected the write.
- How do I fix a 507 error?
- Free up space in your account if the service shows a quota — delete old files or empty the trash
- Is 507 a client error or a server error?
- 507 is in the 5xx range, which means server error. The request was acceptable but the server could not fulfil it, so retrying later can succeed.
Related pages
- 500 Internal Server Error Something went wrong on the server and it has no more specific code to describe
- 502 Bad Gateway A proxy or gateway reached the server behind it and got back a broken response,
- 503 Service Unavailable The server is temporarily unable to handle the request, usually because it is ov
- 504 Gateway Timeout A proxy or gateway waited for the server behind it and gave up before an answer
- 524 A Timeout Occurred Cloudflare connected to the origin successfully but the origin did not finish re
- 521 Web Server Is Down Cloudflare could not connect to the origin server because it refused the connect
- 522 Connection Timed Out Cloudflare tried to open a connection to the origin server and never got a reply
- 520 Web Server Returned an Unknown Error Cloudflare reached the origin server but got back a response it could not make s
- 525 SSL Handshake Failed The TLS handshake between Cloudflare and the origin server failed.
- 526 Invalid SSL Certificate The origin server presented a TLS certificate that Cloudflare could not validate
- 530 Origin DNS Error A Cloudflare error shown alongside a 1xxx error code that carries the real expla
- 501 Not Implemented The server does not support the functionality needed to fulfil the request, usua