Loading…
Loading…
Status
No wall of evergreen badges. This page runs a real health check against AGI’s hosted services at most once a minute, shows you when that check ran, and tells you exactly what it does not cover. Most of AGI doesn’t depend on our servers at all : Local and BYOK work runs on your device.
Live signal
The result below comes from a real run of the checks, shared by everyone who loads this page inside the same window: the “Checked” column is the moment it actually ran, not the moment you asked. It calls the health checks directly, in-process, rather than making an HTTP request to our own health endpoint. Building a request URL out of inbound headers is a server-side request forgery vector, so a status page that self-fetches is a status page with a security bug. Running them once per window rather than once per visitor also keeps a traffic spike on this page from becoming load on the very dependencies it is reporting on. Same checks the monitored endpoint runs. Not a hand-edited badge.
| Scope | Result | Checked |
|---|---|---|
| Hosted platform | Operational | Thu, 03 Sep 2026 06:11:19 GMT |
| Configuration | Passing | Thu, 03 Sep 2026 06:11:19 GMT |
| Postgres | Passing | Thu, 03 Sep 2026 06:11:19 GMT |
| Payments | Passing | Thu, 03 Sep 2026 06:11:19 GMT |
Every check below passed on the most recent run.
Scope of the check
A green row here is worth exactly three checks, so here they are. Reading it as whole-platform coverage would be reading it wrong.
| Covered | What the check actually does |
|---|---|
| Configuration | A database connection string is present in the serving environment. |
| Postgres | A query is executed against the primary database and returns. |
| Payments | A read call to the payments API returns. A failure here degrades billing only: chat is unaffected, so it does not report a platform outage. |
| Not covered | Authentication (Clerk) · Object storage (Cloudflare R2) · The API gateway · The rate limiter (Redis) · Individual model providers and model routes · Desktop, mobile, extension, and CLI surfaces. A green signal above says nothing about any of these. If one of them is failing for you, the report channel below is the fastest path. |
What depends on us
The three trust modes have different failure domains. An incident on our side does not touch work that never leaves your device.
Local
Local chats, files, and sessions run on your own hardware through Ollama or LM Studio. They keep working during any hosted incident, including a full outage.
BYOK
BYOK requests on Desktop, CLI, and VS Code travel directly from the local runtime to the provider you chose. If a model misbehaves, the provider’s own status page is the source of truth.
AGI Cloud
Managed compute is in public alpha: signed-in users can use it now, with metered usage and visible provider labels. This is the only mode the signal above describes.
Incidents
We have not published an incident archive or postmortems. Rather than leave that as an implied “no incidents ever”, here is the process and the commitment, so you can hold us to it.
| Severity 1 | Hosted platform cannot serve, or a confirmed unauthorised access to customer data. We start work immediately on discovery and post here once we can describe the impact accurately. |
| Severity 2 | A major capability is unavailable or badly degraded for many users (for example managed chat, sign-in, or file upload) while the rest of the platform serves. |
| Severity 3 | Degraded or partial function with a workaround, or an issue affecting a narrow set of users. |
| Notification | For a confirmed security incident involving customer personal data, we will notify affected account holders by email at the address on the account, and will do so without undue delay once we have confirmed scope. Where a data protection regulator requires notification, we will meet that obligation. |
| On-call | There is no 24/7 rotation. Response is best-effort during working hours. This is stated plainly because assuming otherwise would be the dangerous reading. |
| Security reports | A suspected vulnerability is not a status incident: it goes through coordinated disclosure, including our scope and safe-harbour terms, on /security. |
Report something
Release notes live in the changelog, and a human reads every incident report. Tell us what you saw and when. We’d rather hear it twice than not at all.