> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mediamonster.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Status

> Whether the API, database, storage, queue and encoders are up — as a page at mediamonster.app/status and as JSON at GET /api/v1/status.

[mediamonster.app/status](https://mediamonster.app/status) shows the health of each part of Mediamonster, checked live. The same report is JSON at `GET /api/v1/status`, for your own monitors.

```bash theme={"theme":{"light":"github-dark","dark":"github-dark"}}
curl https://mediamonster.app/api/v1/status
```

```json theme={"theme":{"light":"github-dark","dark":"github-dark"}}
{
  "status": "operational",
  "summary": "All systems operational",
  "checked_at": "2026-09-26T12:00:00.000Z",
  "components": [
    { "id": "api", "name": "API", "status": "operational", "note": "Answering requests.", "latency_ms": 0 },
    { "id": "database", "name": "Database", "status": "operational", "note": "Answering queries.", "latency_ms": 41 },
    { "id": "storage", "name": "Storage", "status": "operational", "note": "Reading and writing files.", "latency_ms": 63 },
    { "id": "queue", "name": "Queue", "status": "operational", "note": "Last scheduled run 6 min ago.", "latency_ms": 58 },
    { "id": "render", "name": "Render", "status": "operational", "note": "Render service answering.", "latency_ms": 120 }
  ],
  "uptime_targets": [
    { "plan": "Kraken", "target": "99.9%" },
    { "plan": "Behemoth", "target": "99.9%" },
    { "plan": "Cyclops", "target": "Best effort" },
    { "plan": "Minotaur", "target": "Best effort" }
  ]
}
```

It needs no key, and answers `200` whatever it says: the request worked, and the body is the news. Alert on `status`. The report is reused for 30 seconds, so polling it more often than that tells you nothing new.

If your monitor can only read status codes, add `strict=true`. It then answers `503` when `status` is `down`, with the same body. `degraded` and `unknown` still answer `200`.

```bash theme={"theme":{"light":"github-dark","dark":"github-dark"}}
curl -i "https://mediamonster.app/api/v1/status?strict=true"
```

Incidents, planned maintenance and uptime history are written up at [status.mediamonster.app](https://status.mediamonster.app/), which is hosted apart from Mediamonster and stays up when it doesn't. You can subscribe to updates there.

## Components

| `id` | What it covers | How it is checked |
| - | - | - |
| `api` | The REST API, the MCP server and the app | The check is answered at all |
| `database` | Accounts, keys, credits, recipes, the Vault index | One small query |
| `storage` | Every file: uploads, results, the Vault | One read of a known file |
| `queue` | Background runs, webhooks, automations | A heartbeat is written every 15 minutes. One older than 35 minutes reads as degraded |
| `render` | The video and audio encoders | Their health check |

Each check has four seconds to answer, or it counts as `down`.

## States

| `status` | Means |
| - | - |
| `operational` | Working |
| `degraded` | Working, but slow or behind — background work may be late |
| `down` | Not answering |
| `unknown` | The check couldn't tell. It doesn't change the overall state |

The overall `status` is `down` when the API, the database or storage is down, since nothing runs without them. Any other component that isn't operational makes it `degraded`.

## Uptime targets

Kraken and Behemoth are built to **99.9%** monthly uptime; Cyclops and Minotaur are best effort. These are targets, not a credit-backed guarantee — see the [Terms](https://mediamonster.app/terms).

During an incident, a failed run's credits go back automatically. If something looks wrong and the page says otherwise, [tell us](https://docs.mediamonster.app/help/support.md) with the `X-Request-Id` of a failing call.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.