Status

Is it working?

The current state of every service, and how we check it. We do not run a monitoring probe yet, so there are no uptime percentages here — we would rather show you nothing than a number nobody measured.

Report a problem Read the roadmap

API

The service the product and every agent run talks to.

Operational

Web application

The board, plans, reports and everything you click.

Operational

Agent run scheduler

Dispatches tasks to specialists and holds work that is waiting on a dependency or a gate.

Operational

Deployment pipeline

Merges approved branches, runs your deploy command, your health check and, when needed, your rollback command.

Operational

Investigations

Opens on a failed run, reads logs and diagnostics at read-only access, and writes up what it found.

Operational

Git integrations

Cloning, branching, worktree creation and pushing against your connected repositories.

Operational

Notifications

In-product alerts: a plan awaiting approval, a gate opened, a health check failed. Slack delivery is roadmap, not shipped.

Operational

Bars cover the last 90 days, one bar per period, newest on the right. These are observed figures describing what happened. They are not a service level agreement, they carry no remedies, and we do not offer one — see the roadmap for where a contractual SLA sits.

Definitions

What each status level means

So that "degraded" means the same thing on this page every time.

Operational

The service is doing what it is supposed to, at normal speed. This is the only level at which we say nothing is wrong.

Degraded

The service works, but slowly or unreliably — retries, queueing, longer waits. Your work completes; it takes longer than it should. A single slow health check counts here.

Partial outage

Some part of the service is unavailable, or it is unavailable for some customers. Example: runs dispatch normally but deployment runs cannot start.

Major outage

The service is unavailable for most or all customers. Agent runs do not start, and anything mid-flight is held rather than abandoned. We post here first and write to affected teams next.

Maintenance

Planned work with a known window, announced in advance. We schedule it outside European and North American working hours, and we never begin maintenance while a deployment run is in flight.

How this page is made

Two things you should know before trusting it

This page is updated by hand. There is no automated feed behind it yet. A person checks the services and edits the page, which means it can lag reality by minutes during an incident and it will never update at 4am on its own. Treat the product itself as the authority on whether your run is moving. An automated status feed, with subscriptions and a machine-readable endpoint, is on the roadmap.

Observed uptime is not a promise. The percentages above describe what we measured. They are not a commitment, they carry no service credits, and no contract refers to them. We do not offer a contractual uptime SLA today and we say so on the pricing page as well as here.

Seeing something we are not?

Tell us what you are seeing and roughly when it started. Include a run or deployment reference if you have one. A person reads it.

Report a problem Ask the community

Incidents written up within two working days · No blame, named systems