← All HTTP status codes
2042xx — Success
HTTP 204 No Content
The request succeeded but the response intentionally has no body. Common for DELETE.
What it means
204 No Content tells the client "done, nothing to return." The response must have no message body — clients shouldn't try to parse one. Standard for DELETE operations and for PUT/PATCH endpoints that don't echo the updated resource.
If your client is choking trying to JSON.parse a 204 response, that's the bug — switch to checking status before parsing, or have the server return 200 with a body if a body is expected.
Common causes
- DELETE request that successfully removed a resource
- PATCH request that updated state but doesn't return the entity
- CORS preflight responses that don't need a body
How Uptimera reports 204
Uptimera treats 204 as healthy.
Catch 204s before your customers do
Uptimera monitors your URLs from multiple regions and alerts the moment a 204 starts firing. Free plan included.