507 Insufficient Storage
5xx server error
The server can't store what's needed to complete the request.
507 comes from WebDAV (RFC 4918): the server can't save what you're uploading — the disk is full, or the user's quota is used up. Some APIs reuse it for storage-quota errors.
| Class | 5xx Server Error |
|---|---|
| Retry? | No — change the request first |
| Cacheable by default | No — only with explicit Cache-Control |
| Response body | Allowed |
| Defined in | RFC 4918 §11.5 — 507 Insufficient Storage |
Example response
HTTP/1.1 507 Insufficient Storage
Content-Type: application/json
Content-Length: 32
{"error":"Insufficient Storage"}Common causes
- A full disk on the server.
- Per-user storage quotas exceeded on file-sync services.
How to fix it
- Free up space or raise the quota.
- Operators: monitor disk usage — logs and temp files fill disks quietly.
Send a 507 from your server
Express
res.status(507).json({ error: "Insufficient Storage" });Next.js route handler
return Response.json({ error: "Insufficient Storage" }, { status: 507 });Flask
return {"error": "Insufficient Storage"}, 507Go net/http
http.Error(w, "Insufficient Storage", http.StatusInsufficientStorage)
nginx
return 507;
Check what a URL returns
Print just the status line from the command line, or check a whole list of URLs at once, with their response headers, in the HTTP Status Checker.
curl -sI https://example.com/your-path | head -n 1
Frequently asked questions
Is 507 temporary?
It lasts until space is freed. Retrying immediately won't help.
Related status codes