System status

Current posture: operational.

This is a lightweight status page. It states our general operational posture and links to a live health endpoint you can query yourself. It does not publish uptime percentages or a historical incident record, and it is not updated automatically in real time.

All systems operational

Reflects our general posture. For a real-time, machine-readable check, query the health endpoint below.

Components

Service components.

Each component is shown with a generic operational state — we do not attach invented uptime or latency numbers.

  • Web app
    The dashboard and public site
    Operational
  • API
    Application endpoints and request handling
    Operational
  • Database
    Primary Postgres data store
    Operational
  • AI features
    Protocol generation, refine, and the assistant
    Operational
Live check

The authoritative real-time signal.

Rather than a hand-updated dashboard, we expose a health endpoint you can query directly. It is the source of truth for whether the service is up right now.

GET /api/health

Liveness. Returns 200 whenever the app is serving requests.

Open live check →
GET /api/health?deep=1

Readiness. Also checks database reachability and returns 503 if the data store is unreachable.

Open readiness check →
What this page is — and isn't

A lightweight status page.

  • We do not publish uptime percentages, latency figures, or a historical incident timeline — we would rather show nothing than a number we cannot stand behind.
  • The component states above reflect our general posture, not a live automated probe. For real-time truth, use the health endpoint.
  • A full status service — automated monitoring, per-component history, and subscribable incident notifications — is planned.

Experiencing a problem? Email support@oltodiscovery.com and we will look into it.