507 Insufficient Storage

The server has no space left to store what the request needs.

Code: 507
Reason phrase: Insufficient Storage
Class: 5xx Server error
Defined in: RFC 4918 section 11.5
Cacheable by default: No

What it means

Server error: the request may be fine, but the server failed to carry it out.

Common causes. A full disk on a WebDAV or file storage server.

What to do. Free up space on the server.

How clients and crawlers treat it

Google Search. Googlebot treats 5xx responses as a sign of trouble and temporarily slows its crawl rate. Already indexed URLs are kept at first, but are dropped if the errors continue. Source: Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search.

Caching. Not cacheable by default (RFC 9110 section 15.1 does not list it). A cache stores it only when the response says so with Cache-Control or Expires.

Example response

HTTP/1.1 507 Insufficient Storage
Content-Type: text/plain; charset=utf-8

Insufficient Storage

How to send 507

nginx

location /example {
    return 507;
}

Apache (.htaccess)

RewriteEngine On
RewriteRule ^example$ - [R=507,L]

PHP

http_response_code(507);
echo 'Insufficient Storage';
exit;

Node.js

res.writeHead(507, { 'Content-Type': 'text/plain' });
res.end('Insufficient Storage');

Python (Flask)

# in a view function
return 'Insufficient Storage', 507

Change the paths to suit. In nginx, add_header needs always to apply to error responses.

Related codes

All status codes · All 5xx codes

Names and numbers from the IANA HTTP Status Code Registry. Google Search behaviour as documented by Google Search Central.