2xx Success
HTTP 207 Multi-Status
A WebDAV response with an XML body that holds separate status codes for several resources or operations, such as the files in a folder. A 207 on its own doesn’t mean everything worked: some of the statuses inside it can be failures.
Defined in RFC 4918, section 11.1(opens in a new tab)
//_01 Uptime checks
Is 207 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 207 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 207 and what to do
Typical causes
- WebDAV clients and servers: file sync tools, calendar and contacts servers (CalDAV, CardDAV).
If you run the site
- Read the statuses inside the body; the 207 itself only says the response has several.
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 207 mean?
A WebDAV response with an XML body that holds separate status codes for several resources or operations, such as the files in a folder. A 207 on its own doesn’t mean everything worked: some of the statuses inside it can be failures.
Does an uptime monitor count 207 as down?
Up. By default an Uptimecheck HTTP monitor accepts 200–399 as up, so a 207 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