2xx Success
HTTP 201 Created
The request succeeded and created one or more new resources, typically after a POST or PUT. The new resource is identified by the Location header, or by the request URL when there is none.
Defined in RFC 9110, section 15.3.2(opens in a new tab)
//_01 Uptime checks
Is 201 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 201 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 201 and what to do
Typical causes
- An API call or form that creates something: an account, an order, an upload.
If you run the site
- Send a Location header pointing at the new resource, so clients don’t have to guess its URL.
If you’re a visitor
- Nothing to do: whatever you submitted was created.
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 201 mean?
The request succeeded and created one or more new resources, typically after a POST or PUT. The new resource is identified by the Location header, or by the request URL when there is none.
Does an uptime monitor count 201 as down?
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 201 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