2xx Success
HTTP 204 No Content
The request succeeded and the server has nothing to send in the body. It is common for DELETE requests, for saves made by JavaScript and for analytics beacons. A browser that gets a 204 for a link or form stays on the current page.
Defined in RFC 9110, section 15.3.5(opens in a new tab)
//_01 Uptime checks
Is 204 up or down for a monitor?
Uptimecheck HTTP monitor
Default settings
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 204 counts as up. With a keyword check, the page must also contain the word you set.
Is it down? checker
Free, at /is-it-down/
Up: the checker counts any answer below 500 as the site answering.
//_02 Causes and fixes
Why you see 204 and what to do
Typical causes
- An API call that saves or deletes something, or a tracking endpoint.
If you run the site
- A 204 never has a body, so a keyword check on a URL that answers 204 always fails. Monitor it by status alone.
If you’re a visitor
- Nothing to do.
Know the moment your site stops answering as it should
An Uptimecheck monitor requests your page as often as every minute, checks the status code against the ones you expect, confirms a failure with a second check and then alerts you.
14-day free trial · No credit card required
Questions
What does HTTP 204 mean?
The request succeeded and the server has nothing to send in the body. It is common for DELETE requests, for saves made by JavaScript and for analytics beacons. A browser that gets a 204 for a link or form stays on the current page.
Does an uptime monitor count 204 as down?
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 204 counts as up. With a keyword check, the page must also contain the word you set.
Downtime is obsolete.
Set up your first monitor in under a minute, or look around the live demo first.
14-day free trial · No credit card required