Outages Live

io.github.boristane/outages-liveVersion 1.0.0

Is it down? Live status and outages of 259 cloud, AI and developer providers, from status pages.

Status

Responds119 msNov 14, 2026, 14:46 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:46 UTC
Latency: 119 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://outages.live/mcpResponds119 msNov 14, 2026, 14:46 UTC

No sign-in

Claude Code

claude mcp add --transport http outages-live https://outages.live/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: outages-live
Remote MCP server URL: https://outages.live/mcp

Cursor

{
  "mcpServers": {
    "outages-live": {
      "url": "https://outages.live/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"outages-live","type":"http","url":"https://outages.live/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

5 tools

Tools of Outages Live
	Description		Read-only	Idempotent	Open world
`get_provider`Get one provider (for example GitHub, AWS, Vercel, OpenAI): a one-line verdict on whether it reports a problem now, its active incidents, what people reported about it on outages.live in the last 24 hours (reviewed reports only, with a spike flag when many arrive in an hour), maintenance in progress, its last 10 incidents, and 90 days of daily history. Give region or component to keep only active incidents that name it, for example us-east-1 or Actions. Call it when a request to the provider fails, before you change code. An unknown name returns every tracked id.	Get one provider (for example GitHub, AWS, Vercel, OpenAI): a one-line verdict on whether it reports a problem now, its active incidents, what people reported about it on outages.live in the last 24 hours (reviewed reports only, with a spike flag when many arrive in an hour), maintenance in progress, its last 10 incidents, and 90 days of daily history. Give region or component to keep only active incidents that name it, for example us-east-1 or Actions. Call it when a request to the provider fails, before you change code. An unknown name returns every tracked id.	No	Yes	Yes	No
`list_feed`List incidents across providers, the most recently updated first. By default only incidents that are open now. Narrow it with providers, category, and a minimum impact; set state to recent to add incidents resolved in the last days. When the server URL sets filters, they apply to each argument you do not give.	List incidents across providers, the most recently updated first. By default only incidents that are open now. Narrow it with providers, category, and a minimum impact; set state to recent to add incidents resolved in the last days. When the server URL sets filters, they apply to each argument you do not give.	No	Yes	Yes	No
`report_affected`Tell outages.live that an outage affects your user, as the "I'm affected" button on the outage page does. Call it only when your user says that the outage affects them, never on your own. Give the outage id that get_provider or list_feed returns. The count shows on the outage page at once, and each user counts once for each outage, so a second call changes nothing. Returns the new affected count.	Tell outages.live that an outage affects your user, as the "I'm affected" button on the outage page does. Call it only when your user says that the outage affects them, never on your own. Give the outage id that get_provider or list_feed returns. The count shows on the outage page at once, and each user counts once for each outage, so a second call changes nothing. Returns the new affected count.	No	No	Yes	Yes
`report_outage`Report that a provider does not work for your user, as "Report an outage" on outages.live does, also when its status page shows no problem. Call it only when your user asks you to report it, never on your own. The outages.live team reviews each report, and only approved reports show on outages.live, in the API, and in get_provider. One report for each provider each hour.	Report that a provider does not work for your user, as "Report an outage" on outages.live does, also when its status page shows no problem. Call it only when your user asks you to report it, never on your own. The outages.live team reviews each report, and only approved reports show on outages.live, in the API, and in get_provider. One report for each provider each hour.	No	No	No	Yes
`send_feedback`Send feedback to the outages.live team: a provider to add, data that looks wrong (a status that does not match the provider's own page, a missing or stale incident), or an idea. The team reads every message. Send only what the user agreed to share.	Send feedback to the outages.live team: a provider to add, data that looks wrong (a status that does not match the provider's own page, a missing or stale incident), or an idea. The team reads every message. Send only what the user agreed to share.	No	No	No	No

Details

Registry status: Active
Published: Nov 3, 2026
Updated: Nov 3, 2026
Website: https://outages.live/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Developer tools Cloud and infrastructureSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing