HTTP 507 Insufficient Storage

The server cannot store the representation needed to complete the request — it has run out of space.

Defined in RFC 4918 §11.5 — 507 Insufficient Storage · MDN reference

Where you meet HTTP 507 in production

WebDAV and file storage servers with full disks or per-user quotas, and upload services that report quota exhaustion this way.

Why you would test it

Simulates a full disk or an exhausted quota on upload. Check that the client keeps the user's data and explains the problem, rather than discarding the upload.

What your client should do about a 507

Retrying immediately will fail. Free space or ask for more quota, then retry. Keep the data client-side so it is not lost.

507 versus the codes it gets confused with

• 507 vs 413 Content Too Large — 413 means this request is too large. 507 means the server has no room, whatever the size.
• 507 vs 503 Service Unavailable — 503 is general unavailability; 507 names storage as the cause.

Endpoints that return 507

1 endpoint in this playground answers with 507. Every one is free, needs no signup, and can be called from the browser or with curl.

• GET https://funapi.dev/api/faults/v1/status/{code} — Returned on request (Fault Injection API) Open & run this endpoint

Questions about HTTP 507

Is 507 my fault or the server's?

The server's capacity, or your quota on it — not the request's format.

Is 507 only for WebDAV?

It was defined by WebDAV, but storage APIs use it for quota exhaustion too.

Other server error codes

• 500 Internal Server Error
• 501 Not Implemented
• 502 Bad Gateway
• 503 Service Unavailable
• 504 Gateway Timeout
• 505 HTTP Version Not Supported
• 508 Loop Detected
• 511 Network Authentication Required

All HTTP status codes · All 39 mock REST APIs · Getting started guide

Last updated 2 October 2026