Skip to main content
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.
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.
Incidents, planned maintenance and uptime history are written up at status.mediamonster.app, which is hosted apart from Mediamonster and stays up when it doesn’t. You can subscribe to updates there.

Components

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

States

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. During an incident, a failed run’s credits go back automatically. If something looks wrong and the page says otherwise, tell us with the X-Request-Id of a failing call.