-
Loading
Reading
/api/health… unknown
Recent history
OGUM does not keep a public incident log yet, so this history is built by your own browser while this page is open — one check every 30 seconds, kept locally. It is a useful sanity check during an incident, not an authoritative uptime record.
How to read this
- API — whether this server answered at all.
/api/healthanswers503by design when object storage is degraded, so a 503 still counts as the API being up; the storage row is where that shows. - Database — Postgres holds credits, jobs and your history. When it is down, generation is refused before any credits are touched.
- Object storage — where finished deliverables live. Degraded means the server fell back to local container disk: documents generated during that window can be lost on the next restart.
- Generation — live means real models are producing deliverables. Mock mode means the instance has no API key and is returning clearly-labelled placeholders; the app flags those documents too.
Services OGUM depends on
Most OGUM incidents start somewhere else. If a row above is red, check these before writing in:
- Anthropic — generation
- Railway — hosting, Postgres, storage
- Auth0 — sign-in
- Stripe — billing
- Resend — email
Something is broken and this page says everything is fine
This page only knows what the server can see about itself. If your experience disagrees with it, that is worth knowing — email support@ogum.org with what you were doing and roughly when. A failed generation refunds its credits automatically, so you are not charged for an outage.