416 Range Not Satisfiable
The server cannot fulfill the requested byte range for the resource.
Definition (RFC 9110)
HTTP status code 416 416 Range Not Satisfiable is defined in RFC 9110 (HTTP Semantics), Section 15.5.17 — the current authoritative specification for HTTP semantics, published June 2022, which obsoletes the older RFC 7231 and RFC 2616.
Description
416 Range Not Satisfiable (formerly Requested Range Not Satisfiable) is returned when the client requests a byte range using the Range header, but the server cannot serve that range because it falls outside the bounds of the resource. The server should include a Content-Range header indicating the total size of the resource.
Relevant in video streaming, file download resumption, and large file serving.
Common Causes
- Resume download requesting bytes beyond the end of the file
- Video player seeking past the end of the stream
- Stale range request after the file was updated (file shrank)
- Off-by-one error in range calculation
How to Fix
- Check the
Content-Rangeheader in the 416 response for the actual resource size - Re-fetch the resource from the beginning if the range is invalid
- Handle 416 in download clients by restarting the download
- Use
ETagorLast-Modifiedvalidation before resuming
Check your website's HTTP status code
Check now →