Memory and trace store
Schema migration to support per-tenant retention policies. Read availability maintained; writes briefly fall back to local buffer.
We publish live status for every service we operate, plus a rolling history of changes. For paid customers, the same signals are available as Prometheus and OpenTelemetry streams into your environment.
Targets are public. Trailing 30-day actuals are computed continuously. Error budget is the customer's lever — when we burn through it, we slow down.
| Service | Target | Trailing 30d | Budget used |
|---|---|---|---|
| Aether API · availability | 99.95% | 99.98% | 12% |
| Aether API · p50 first-token latency | ≤ 280ms | 210ms | — |
| Aether API · p99 first-token latency | ≤ 2.0s | 1.7s | — |
| Agent runtime · job durability | 99.999% | 99.999% | 3% |
| Memory store · read availability | 99.99% | 99.995% | 8% |
| Customer console · availability | 99.9% | 99.94% | 21% |
We publish every planned maintenance window with at least 72 hours of notice. Customers under SLA also receive direct notification through their account contacts.
Schema migration to support per-tenant retention policies. Read availability maintained; writes briefly fall back to local buffer.
Promotion of Aether 1.0.4 with the long-rollout fix. Blue/green deploy; eval gate must pass for promotion.
We publish a short note for every change that touched a customer surface — and a longer postmortem for anything that broke one.
Rolled out an upgraded acoustic-dispenser driver in three regions. No customer-visible impact; one queued plate held briefly during the swap.
Promoted Aether 1.0 to GA. Inference traffic shifted behind percentage rollout; rollback path retained for a week. No customer-visible regressions detected during ramp.
A regional failover in our cloud provider's storage layer briefly disrupted read availability in EU-West. Reads served from secondary; no writes lost. Postmortem published.
Read the postmortemMigrated control-plane to the new blue/green deploy pipeline. Two minutes of read-only API during cut-over, scheduled and announced.
A regression in the docking agent caused inflated docking scores for a subset of structures. Detected by the eval-gated promotion guard, rolled back automatically. Affected customer runs were re-executed at no charge.