# Requested byte range is not satisfiable

> Canonical HTML: https://screenrig.ai/problems/invalid-range/

HTTP 416 · `invalid_range`

## What it means

The API answers with HTTP 416 Range Not Satisfiable and an `application/problem+json` document when the condition is Requested byte range is not satisfiable. The document's `type` member is `https://screenrig.ai/problems/invalid-range`, the address of this page, and its `code` member is `invalid_range`.

## What to do

The requested byte range starts past the end of the content. Request a range within the content length, or read the whole object.

## Player action

The Player action class is `retry_backoff`: Retry the same request on the backoff schedule, never sooner than Retry-After.

## Reference

| Field | Value |
| --- | --- |
| Code | `invalid_range` |
| HTTP status | `416 Range Not Satisfiable` |
| Type | `https://screenrig.ai/problems/invalid-range` |
| Player action | `retry_backoff` |

- [All problem types](https://screenrig.ai/problems/)
- [API reference](https://screenrig.ai/docs/api/#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)