Status
Operationalchecked
This page is measured, not promised: there is no SLA, and nothing here is a commitment to uptime. What we do commit to is that a generation which fails is never billed — the charge returns to your balance automatically.
A failed cache or storage check degrades part of the product but keeps the site serving; a failed database check means the service is down. The same checks are exposed as JSON at /api/health — it answers 200 while the service is serving and 503 when it is not.
100% of health checks were fully healthy across the days we have samples for. Each bar is one day; grey means no samples were recorded that day.
These numbers are ours, which is exactly why they are worth verifying: point any external monitor at /api/health and you will have an independent record that we cannot edit.
Counted over 3,901 jobs in the last 30 days — the same window in which generation records are kept, so the denominator is not truncated. A safety block is the model refusing a specific prompt rather than a fault on our side; both it and a technical failure return the charge to your balance without a request.
The site returned 502 errors in waves. Generations already running were unaffected and no balance was lost, but the studio and history were unreachable while it happened.
Feed queries pulled oversized model metadata stored alongside each generation, which exhausted the process memory and restarted the app in a loop. The heavy data was moved to a separate table, list queries stopped selecting it, and the feed was switched to cursor paging.
The log is written by hand and entries are not removed once published. It starts where the practice started, so it is not a complete history of everything that ever broke.
No service level, no compensation for downtime, no guarantee that a model provider will have capacity at the moment you need it. The honest counterweights are that failed work is never billed, that unused balance is refundable at any time with no deadline, and that the health endpoint is public so you never have to take a status page's word for it.