Official status pages of 406 cloud, SaaS and developer providers, checked every minute. Model-written summaries are labeled.
latest read 5 providers with a major or partial outage now
Incidents and cascades as the feed lists them, by when each started.
The providers the most builds depend on.
Live, from each provider's official status page.
Drop a package.json, lockfile, Terraform or .env to see which providers you depend on, which have a problem now, and one feed for all of them.
Lockfiles, package.json and .env files are read in your browser, so only package and variable names are sent. Other files are matched and discarded. Only provider names are kept.
Add the down.guide MCP server to Claude Code, Cursor, Codex or another agent so it can ask whether a provider is down and check a whole stack.
Every tool has a REST twin, listed on Agents.
Set up the down.guide MCP server for me. down.guide is a free, public outage feed for 400+ cloud and SaaS providers: no login, no API key. - Server name: down-guide - Transport: Streamable HTTP - URL: https://mcp.down.guide/mcp Add it the way you normally add MCP servers (your CLI command or your MCP config file), then confirm it connects and lists its two tools, search and execute. To finish, use them to run the stack.check operation on this project's package.json or lockfile and tell me which of my providers have a problem right now.
Paste this into any coding agent. It adds the server with its own MCP setup.
Get new outages in a feed reader, Slack or Discord, filtered by provider, category, impact or confidence.
https://down.guide/feed
Copy into your feed reader, or use /feed subscribe in Slack. In Discord, add it with a feed bot such as MonitoRSS.
https://down.guide/feed?format=atom
Copy this URL into a reader that supports Atom.
https://down.guide/feed?format=json
Each entry carries the full incident under _down_guide, for scripts and readers that support JSON Feed.
https://down.guide/api/v1/incidents
Pages of 30 incidents, newest first. Pass the response's next_cursor as cursor for the next page.
Up to 100 incidents from the last 14 days. The live list shows everything open now, and the daily recaps list each day's incidents.
A free outage feed for people and agents. It reads the official status pages of 406 cloud, SaaS and developer providers every minute, normalizes their incidents, and labels its own evidence (visitor reports) as its own.
Each provider's own status page (Atlassian Statuspage, incident.io, Instatus, Better Stack, status.io, and the AWS, Google Cloud, Slack and Salesforce feeds, with RSS as a fallback). Their words are quoted verbatim and linked. down.guide's own evidence is always labeled as ours, with numbers.
Subscribe to a feed; there is no account or webhook to set up. https://down.guide/feed has every incident, /feed?provider=<slug> one provider, and the stack checker builds one feed for all of a project's providers. In Slack, install the RSS app and run /feed subscribe <feed URL> in a channel; in Discord, give the URL to a feed bot such as MonitoRSS. Add format=atom or format=json for Atom or JSON Feed. For scripts, GET https://down.guide/api/v1/incidents takes the same filters and pages by 30 (pass next_cursor back as cursor). To get them by email instead, use the Email tab of the subscribe form on the homepage: Instant for one or more providers (a new or worsening incident, at most one email every 15 minutes), or Daily or Weekly at 9:30am Pacific.
From each provider's own incidents, per component, the way Statuspage computes its own: a major outage counts as full downtime and a partial outage as 30%; degraded performance and maintenance don't count. An incident counts against the components it names, and one that names none counts as a single component unless the page lists no components at all. An incident whose updates or components name only cloud regions, under a title that doesn't (us-east-1, europe-west2), is a regional outage: it counts as a partial outage at most, and only for that share of the provider's regions, so one AWS region down isn't all of AWS down. Minor or regional issues (below) never count. The window starts at the provider's first data point.
An MCP server at https://mcp.down.guide/mcp (also /mcp on this site), a REST API under /api/v1 with the same JSON as each MCP tool, RSS/Atom/JSON feeds you can filter by provider, category, impact, region or your stack, and a .md copy of every page.
Nothing, and there's no account to make. There is no token or coin, and there never will be.
Sazabi, which builds AI-native observability and security. down.guide is a free Sazabi Labs project, like cve.now. It uses no Sazabi customer data.