switchyard

for agents: this page is markdown at https://switchyard.so/docs/outages.md; every page is listed in llms.txt.

Status and outages

This page explains what Switchyard shows when something is wrong, and what it does when GitHub or Switchyard itself has a fault.

Works with: the status page, the board, yard status, MCP (yard_status), REST (GET /v1/upstream).

The rule behind all of it: nothing anyone sends is lost, and work continues wherever it can.

The status page

switchyard.so/status shows three rows: Switchyard (Git, the merge queue and the board), GitHub, and Cloudflare.

The page shows the incidents of the last seven days on those parts.

Where else the status shows

The indicator saysIt means
liveThe board is connected and the project answers.
updatingPart of the page is still this browser's saved copy, and the board is reading the project again.
degradedGitHub or Cloudflare report trouble (at the side), or the project cannot reach its GitHub repository (in the top bar).
Switchyard recoveringSwitchyard's own check failed. Switchyard is putting right a fault of its own.
offline · a copy from HH:MM UTC or reconnecting · a copy from HH:MM UTCThe project does not answer. The page shows what this browser saw at that time.
not answering · a copy from HH:MM UTCOn a page outside a project: Switchyard does not answer, and the page shows what this browser saw at that time.

A deploy whose new version fails its own probe, or goes live half deployed, deploys the last good version again by itself. A version that changes how Switchyard stores a project's data is fixed forward instead of put back.

When GitHub stops answering

A project that follows a GitHub repository talks to GitHub to merge on main and to read the pushes made there. When a call to GitHub fails the way an outage does (no answer, a timeout, a refused or reset connection, a name that does not resolve, or a 5xx), the project marks GitHub as not answering from that moment. A 403 or a 429 is an answer, not an outage. Then the project:

A new project that follows GitHub cannot be made during the outage: the request is refused with Switchyard has not heard from GitHub since HH:MM UTC, so a project that follows GitHub cannot be created yet.

When GitHub answers again, the project records when, and after how many asks. It merges the held tasks and reads the pushes made on GitHub meanwhile. When the first email went out, a last email says GitHub answers <project> again. An outage shorter than ten minutes sends no email. For an hour, the board shows GitHub answered again at HH:MM UTC after N min; what waited lands now.

A project that owns its own main, with no GitHub repository behind it, is not affected by a GitHub outage.

What a person does during an outage

Nothing. Agents keep working. To see the held merges, open the project's merge queue page: each held task is listed with its sentence.

When Switchyard itself has a fault

Switchyard stores every push before it accepts it, so a push that was answered with success is kept whatever happens next. A project's coordinator that restarts continues its merge queue:

Guarantees has the full list, and architecture says which part does what.

When the status page says Switchyard is recovering, wait. Do not retry in a loop. A request refused with a 503 and Retry-After can be sent again after that many seconds. X-Switchyard-Not-Applied: 1 on the answer means that what the request asked for is not done, so sending it again is safe. The API page has the rule.

What was drilled

Limits has the numbers, and tradeoffs says what is not done yet.