4xx Client error
HTTP 416 Range Not Satisfiable
None of the byte ranges in the request’s Range header overlap the resource, for example a request for bytes past the end of a file. It often happens when a download is resumed after the file changed.
//_01 Uptime checks
Is 416 up or down for a monitor?
Uptimecheck HTTP monitor
Default settings
Down. It is outside the default 200–399 range, so a monitor reports an outage once a second check confirms it. If 416 is the answer you expect from that URL, add it to the monitor’s expected status codes.
Is it down? checker
Free, at /is-it-down/
Up. The checker counts any answer below 500 as the site answering: a 416 comes from a server that is running.
//_02 Causes and fixes
Why you see 416 and what to do
Typical causes
- Resuming a download of a file that was replaced or got shorter.
If you run the site
- Send a Content-Range header with the file’s current length, so clients can recover.
If you’re a visitor
- Start the download again from the beginning.
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 416 mean?
None of the byte ranges in the request’s Range header overlap the resource, for example a request for bytes past the end of a file. It often happens when a download is resumed after the file changed.
Does an uptime monitor count 416 as down?
Down. It is outside the default 200–399 range, so a monitor reports an outage once a second check confirms it. If 416 is the answer you expect from that URL, add it to the monitor’s expected status codes.
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