2xx Success
HTTP 200 OK
The request succeeded. What the body holds depends on the method: for GET it is the page or resource itself, for POST the result of the action. It is the status almost every working page answers with.
Defined in RFC 9110, section 15.3.1(opens in a new tab)
//_01 Uptime checks
Is 200 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 200 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 200 and what to do
Typical causes
- A normal, successful request.
If you run the site
- A 200 doesn’t prove the page is right. An error message, an empty page or a “not found” page served with 200 (a soft 404) looks healthy to a check that only reads the status.
- Add a keyword check to an HTTP monitor so it also fails when a word that should be on the page is missing.
If you’re a visitor
- Nothing to do: the server answered as it should.
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 200 mean?
The request succeeded. What the body holds depends on the method: for GET it is the page or resource itself, for POST the result of the action. It is the status almost every working page answers with.
Does an uptime monitor count 200 as down?
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 200 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