507 Insufficient Storage

HTTP response status code 507 Insufficient Storage is a server error indicating the server does not have enough storage space to complete the request.

Table of Contents

Usage

The 507 Insufficient Storage status code means the server does not have enough storage space to accommodate the HTTP request. This applies to a PUT or POST request normally valid and within the client's quota, but failing because the server's storage is full. The status was designed as part of the WebDAV specification, and the condition is expected to be temporary.

The client request must not be repeated until subsequently requested by a different action.

A related client error is 413 Content Too Large (renamed from "Payload Too Large"), indicating the request content exceeds server-defined limits. While 507 signals the server's storage is full, 413 means the individual request body is larger than what the server is willing to process.

SEO impact

Search engines treat 507 the same as other 5xx server errors. Persistent failures reduce crawl rate and eventually remove affected URLs from the index.

Example

The HTTP client attempts to transfer a file and the server responds with a 507 Insufficient Storage status code because the server is out of storage space.

Request

PUT /docs HTTP/1.1
Host: www.example.re
Content-Type: application/pdf
Content-Length: 10000

<PDF file included in message body>

Response

HTTP/1.1 507 Insufficient Storage
Content-Type: text/html
Content-Length: 181

<html>
  <head>
    <title>Insufficient Storage</title>
  </head>
  <body>
    <p>The server has temporarily run out of
    space and the file transfer failed.</p>
  </body>
</html>

How to fix

The server ran out of storage while processing the request. Restore capacity, then prevent recurrence.

Immediate fixes:

  • Free disk space. Run df -h to identify full partitions. Common space consumers:
    • Log files under /var/log/ growing without rotation. Configure logrotate with maxsize and rotate directives.
    • Temporary files in /tmp or application cache directories left behind after crashes.
    • Old backups or database dumps stored on the same volume as the application.
  • Clear WebDAV trash and versioning data. Nextcloud and other WebDAV servers maintain file version histories and a trash bin. Purge old versions and empty the trash to reclaim space.
  • Raise storage quotas. If the WebDAV server enforces per-user or per-collection quotas, increase the quota in the server's admin panel or configuration file. In Nextcloud, adjust the quota under user settings.

Diagnosing the cause:

  • Run du -sh /* and drill down into the largest directories to find what consumed the space.
  • Check for inode exhaustion with df -i. A filesystem with free bytes but zero free inodes still fails writes.
  • Review application logs for repeated large uploads or runaway processes writing data in a loop.

Preventing recurrence:

  • Set up disk usage monitoring with alerts at 80% and 90% thresholds.
  • Move large static assets or uploaded files to object storage (S3, GCS, Azure Blob) instead of local disk.
  • Implement upload size limits at the application layer to prevent individual requests from exhausting remaining space.

Code references

.NET

HttpStatusCode.InsufficientStorage

Rust

http::StatusCode::INSUFFICIENT_STORAGE

Rails

:insufficient_storage

Go

http.StatusInsufficientStorage

Symfony

Response::HTTP_INSUFFICIENT_STORAGE

Python3.5+

http.HTTPStatus.INSUFFICIENT_STORAGE

Apache HttpComponents Core

org.apache.hc.core5.http.HttpStatus.SC_INSUFFICIENT_STORAGE

Angular

@angular/common/http/HttpStatusCode.InsufficientStorage

Takeaway

The 507 Insufficient Storage status code is a server error indicating the request failed because the server has run out of storage space, and the condition is expected to be temporary.

See also

Last updated: March 11, 2026