Skip to content

Status

Operational status without theater.

Current public status: degraded. This page shows live readiness, recent self-monitoring signals, and append-only history without claiming more precision than Luota can prove.
Report an issueStatus JSONOperational proof

Current status

DegradedLast checked Jun 4, 2026, 5:56 PM

This is a live production read from the web app, API health endpoint, database, worker freshness metric, and Luota's own production monitors. It is not a third-party SLA page yet.

Public web app

This page was rendered by the production web app.

Jun 4, 2026, 5:56 PM

API

API health endpoint returned OK.

Jun 4, 2026, 5:56 PM

Database

Database connection accepted a lightweight read.

Jun 4, 2026, 5:56 PM

Worker freshness

Latest evaluator metric was 37s ago.

Jun 4, 2026, 5:56 PM

Production self-monitoring

Luota monitors Luota.

Current status follows live readiness and the latest dogfood self-check. The 24-hour count is historical evidence: older failed check points stay visible without overriding a recovered current state.

No production self-check results have been recorded in the last 24 hours.

Billing webhook readiness

Every 30 minutes

Operational

healthy; no public timestamp yet.

Production self-check

Every 15 minutes

Operational

healthy; no public timestamp yet.

Public site heartbeat

Every 15 minutes

Degraded

incident; last signal 241h ago.

Readiness endpoint heartbeat

Every 15 minutes

Degraded

incident; last signal 241h ago.

Append-only history

Status log

Degraded

  1. 2026-04-30 22:49 UTC

    Production verification passed after backend audit hardening

    No customer impactResolved

    The deploy shipped session revocation, tenant invariants, incident uniqueness, worker evaluation sharding, web-vitals rate limiting, explicit database pool timeouts, security CI, and a patched Vite advisory path. Backup, backup freshness, restore drill, deploy smoke, auth, UI, billing, MVP, incident, and Lighthouse checks passed.

  2. 2026-04-30 21:36 UTC

    Production deploy verification passed after hardening deploy

    No customer impactResolved

    The deploy replaced web, API, worker, and ops containers, then passed public health, auth, UI, incident, MVP, billing, and Lighthouse checks. Worker heartbeat metrics were confirmed after the deploy.

  3. 2026-04-30 20:58 UTC

    Login surface returned a generic error during active deployment work

    Operator-onlyResolved

    The live login route briefly showed a generic page-level error while production was behind the current repo state. The follow-up deploy restored the login page and verified smoke-user sign-in.

  4. 2026-04-30 00:00 UTC

    Append-only public status history started

    No customer impactBaseline

    Luota now keeps customer-facing status notes on this page. Entries are newest-first and stay visible after resolution; corrections are appended unless they are typo-only.

Deployment gate

Production deploy verification checks the public health endpoint, web surface, API, incident status flow, MVP workflow smoke, billing, backup freshness, and Lighthouse budgets.

Self-monitoring

Luota monitors its own public site, readiness endpoint, production self-check, and billing webhook readiness on the same monitor model customers use.

Incident communication

During launch, customer-impacting incidents are communicated directly by email to affected workspaces. Operational alerts and support mail go to the Luota support inbox.

Resolved entries stay visible so the status page can be audited later. Generated Jun 4, 2026, 5:56 PM.

Open machine-readable feed