The Vibe Board
Your app leans on other people’s services. When one of them breaks, your app breaks too — and it looks exactly like a bug you wrote. This board shows you which of the eight big ones are up right now, laid out like the departures screen at a train station.
-
Step 1
Check here firstBefore you spend an hour blaming your own code, look at this board.
-
Step 2
Read the wordColour alone never tells you anything. The word always does.
-
Step 3
Then go digIf everything here is fine, the problem really is yours. Now go look.
What the words mean
A departures board is only allowed to say a few things, and each one has to mean something exact. These are ours. Colour is never the only clue — the word is always right there too, so this still works if you cannot tell the greens from the reds.
| Reads as | When |
|---|---|
| ON TIME | No active incident on the components we track, and the provider's own page indicator is clear. |
| DELAYED | Something we track is running slow, or the provider has opened a minor incident. |
| REDUCED SERVICE | Part of the service is out - a partial outage, or a major incident on the provider's page. |
| CANCELLED | A full outage on something we track, or a critical incident. The lamp pulses. |
| RESUMING | The provider has applied a fix and is watching it. Not fixed yet, but no longer broken. |
| ENGINEERING WORKS | Planned maintenance is in progress and nothing worse is happening. |
| NO SIGNAL | We could not reach the feed, could not parse it, or the last good read is over five minutes old. Never read this as healthy. |
“No signal” does not mean everything is fine. It means we could not reach that service, could not make sense of its answer, or the last good reading is over five minutes old. A row like that is telling you it does not know — not that the service is healthy.
The board, in words
Every row above, with what it actually covers and a link to the provider’s own page. If you are reading this without JavaScript, this table is the part that always works — and the official pages below are always the last word. Each service with a feed also has a page of its own, with its open and recent incidents and what to do while it is down: Is it down?
| Service | What this row covers | Now | Official page |
|---|---|---|---|
| ANTHROPIC | Claude itself, the connection your AI tools use to reach it, and Claude Code. | NO SIGNAL | status.claude.com |
| OPENAI | The GPT models, the connection your AI tools use to reach them, and Codex. | NO SIGNAL | status.openai.com |
| Gemini, reached through Google's Vertex service. The Google half of most setups. | NO SIGNAL | status.cloud.google.com | |
| XAI | Grok, and the connection your tools use to reach it. | NO SIGNAL | status.x.ai |
| CURSOR | The editor, the helpers it runs in the cloud, and the Cursor command-line tool. | NO SIGNAL | status.cursor.com |
| GITHUB | Copilot, and the AI models behind it. Not ordinary saving and sharing of code, that is a different row we do not draw. | NO SIGNAL | www.githubstatus.com |
| VERCEL | Builds, deploys, and the copies of your site kept near your visitors. In short, whether your ship button works. | NO SIGNAL | www.vercel-status.com |
| SUPABASE | The database, the login system, and the front door to both. What most vibe-coded apps actually run on. | NO SIGNAL | status.supabase.com |