Status
Live state of the platform and the third parties it depends on.
Checked Sun, 22 Nov 2026 23:19:23 GMT. Build d406b8e, version 0.1.0, uptime 0s.
Platform components
| Component | Status | Latency | Note |
|---|---|---|---|
| Database | healthy | 497 ms | — |
| Authentication | healthy | — | — |
| rateLimiter | healthy | — | distributed (Upstash Redis) |
| llm | healthy | — | 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.
7ea3c09219656c6f…d6d1c8066368cfc1All 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.
| Vendor | Purpose | Status page |
|---|---|---|
| Supabase | Primary database; row-level data store | status.supabase.com |
| Clerk | Authentication (SSO, MFA, session management) | status.clerk.com |
| Vercel | Application hosting (Next.js front-end + edge middleware) | www.vercel-status.com |
| Sentry | Error / exception monitoring | status.sentry.io |
| Better Stack | Logs + uptime monitoring + status page | status.betterstack.com |
| GitHub (Actions, repository) | Source control + CI/CD | www.githubstatus.com |
| Anthropic | AI / LLM-backed features (analysis, narrative generation) | status.anthropic.com |
| OpenAI | Text embeddings for agent retrieval | status.openai.com |
Service-level objectives
- Availability: we do not publish an uptime percentage we cannot yet statistically stand behind. Contractual availability and response-time terms attach at Platform tier and above.
- p95 API latency: <500 ms for read endpoints, <2 s for AI-backed endpoints.
- Incident acknowledgement: design partners get a named-contact commitment: fast acknowledgement, honest status and a written post-mortem. There is no out-of-hours on-call rota today, so we do not publish an acknowledgement time. Our incident-response plan is available to customers on request from security@aegiscompliant.com.
- Backup recovery point: ≤24 h (Supabase daily backups). Our backup and restore procedure is available to customers on request from the same address.
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.