Check your stack
Paste a package.json, lockfile, Terraform or .env names to see which providers you depend on, which have a problem now, and one feed for all of them.
Parsed for provider names only; nothing else is kept.
404 providers · 404 reporting · checked
Live
Happening now
28 open incidents and 16 maintenance windows in progress, worst first. Plus 15 minor or regional issues (one country, region, site, carrier route or asset), on the providers' pages.
- MCGrowth Degradation on AUS4S, AUS6S, AUS20S, AUS26S…
Salesforce says some Marketing Cloud Next customers on the AUS68, AUS72, AUS76, AUS82, AUS84 and AUS86 instances cannot publish email content, and affected content may remain in Processing. The cause has been identified, and a fix is being validated before wider rollout.
- DreamHost Homepage: Service Disruption
- [Google Search API] /goto links returned in organic_results->link
- [Google Search API] The "Site:" Operator is Ignored
- Storage Service Degradation
CoreWeave says storage services in US-EAST-13A were degraded and under investigation as of 15:13 UTC on 2026-11-05. At 16:26 UTC it said the issue is mitigated and it is monitoring the affected services.
- Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures
Temporal Cloud says some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failures. The provider identified the issue and applied a mitigation, and it is now monitoring the results.
- October usage report visualization issue
The provider says an issue with its billing metrics exporter caused October usage to be mis-reported and shown as 0 in the cost management app. It says billing was not affected, and it is still working to backfill the correct data.
- Multiple services are impacted
Brevo says it is investigating an issue affecting Contact Services, Redirection Links, sending for Marketing Email Campaigns and Transactional Emails, forms, automation, segmentation, and events processing, with delays. The root cause is under investigation.
- [Google Trends Trending Now API] All requests failing
SerpApi says all requests to its Google Trends Trending Now API are failing with the error "Failed to retrieve the data." The provider has identified a solution and is reviewing it before deployment, and will post an update once the issue is fixed.
- [Bing Search API] Irrelevant/poisoned search results returned intermittently
SerpApi says its Bing Search API is intermittently returning irrelevant or poisoned search results, a problem it has observed over the last few weeks. The incident is currently in the investigating state, and the provider says its team is working on a fix on priority.
Most used
The providers most builds depend on
Live state, 90-day uptime and one bar per day.
- AWSOperational99.99% 90 days
- Google CloudOperational99.91% 90 days
- Microsoft AzureOperational100.00% 90 days
- CloudflarePartial outage99.99% 90 days
- GitHubOperational99.53% 90 days
- VercelOperational99.99% 90 days
- StripeOperational
- OpenAIOperational99.98% since Aug 10
- AnthropicOperational99.57% 90 days
- SlackOperational100.00% 90 days
- TwilioDegraded99.99% 90 days
- DatadogOperational100.00% 90 days
- providers watched
- 400+
- 404 reporting now
- incidents tracked
- 22,000+
- open right now
- 28
- hours of outages this week
- 350+
- partial or major, per provider
Live, from each provider's official status page.
Connect your agent
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: API and MCP docs.
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 tools, including get_provider, check_stack and list_feed. To finish, use check_stack 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.
Subscribe to a feed
Get every new outage in Slack, Discord or a feed reader. Add ?provider= with a provider's slug (or several, comma-separated) for just those.
https://down.guide/feed
In Slack, install the RSS app and run /feed subscribe https://down.guide/feed in a channel. In Discord, add a feed bot such as MonitoRSS and give it this URL. Or paste it into Feedly or any RSS reader.
https://down.guide/feed?format=atom
The same entries as Atom, for readers that prefer it.
https://down.guide/feed?format=json
The same entries as JSON Feed 1.1, each with the full incident under _down_guide, for scripts.
Frequently asked questions
What is down.guide?
A free outage feed for people and agents. It reads the official status pages of 404 cloud, SaaS and developer providers every minute, normalizes their incidents, and adds its own evidence: probes from four regions, reports from visitors and chatter on Bluesky, Hacker News and Mastodon.
Where does the data come from?
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.
How do I get outage alerts in Slack or Discord?
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.
How is uptime calculated?
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 confined to named cloud regions (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.
How do agents use it?
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.
What does it cost?
Nothing, and there's no account to make. There is no token or coin, and there never will be.
Who runs it?
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.