Status

Live state of the platform and the third parties it depends on.

All systems operational

Checked Sun, 22 Nov 2026 23:19:23 GMT. Build d406b8e, version 0.1.0, uptime 0s.

Platform components

ComponentStatusLatencyNote
Databasehealthy497 ms—
Authenticationhealthy——
rateLimiterhealthy—distributed (Upstash Redis)
llmhealthy—ANTHROPIC_API_KEY present

Audit ledger

The SHA-256 hash-chained audit ledger is the regulator-defensible spine of the platform. This panel surfaces the live chain head and a sampled-row verification. The probe at /api/health/ledger replays a bounded tail of the chain on every call; the row count it actually walked is below, rather than restated here where it could drift from the probe. A verified result covers those rows only: it says none of them has been edited or reordered, and it says nothing about whether new rows are still being written — that is what the entry age below is for.

Status: Chain verified
Total rows: 98841
Head seq: 99500
Head SHA-256: 7ea3c09219656c6f…d6d1c8066368cfc1
Rows verified: 200 of 200 sampled
Latest entry: Sun, 22 Nov 2026 20:07:05 GMT (3 h ago)

All 200 sampled rows reproduced their SHA-256 chain links. This covers the sampled tail only, and says nothing about whether new rows are still being written — see latestAgeSeconds.

Upstream dependencies

Circuit breakers around each external dependency. OPEN means we’ve detected sustained failures and short-circuited calls to that dep (falling back to deterministic heuristics where applicable); HALF_OPEN means we’re probing for recovery. Probe at /api/health/breakers.

The breaker probe did not respond, so this page cannot say what state the dependency breakers are in.

Subprocessor status

Each vendor publishes its own status. We don’t aggregate their pages live (no scraping), but if you’re triaging a degradation these are the canonical destinations. Full subprocessor list with regions and DPA links is at /legal/subprocessors.

VendorPurposeStatus page
SupabasePrimary database; row-level data storestatus.supabase.com
ClerkAuthentication (SSO, MFA, session management)status.clerk.com
VercelApplication hosting (Next.js front-end + edge middleware)www.vercel-status.com
SentryError / exception monitoringstatus.sentry.io
Better StackLogs + uptime monitoring + status pagestatus.betterstack.com
GitHub (Actions, repository)Source control + CI/CDwww.githubstatus.com
AnthropicAI / LLM-backed features (analysis, narrative generation)status.anthropic.com
OpenAIText embeddings for agent retrievalstatus.openai.com

Service-level objectives

Past incidents

No customer-affecting incidents in the last 30 days. Customers with a signed DPA are notified of a personal data breach directly, without undue delay and within the period in clause 3(g) of the DPA ([48] hours in the draft, pending counsel review), followed by a written post-mortem by email.

This page reflects in-app health checks and is updated on every request. For independent uptime monitoring, prospective customers can configure their own probe against /api/health.