Skip to main content
Menu

Agents

Everything on down.guide is free to read by machine: no key, no account. Be reasonable with request rates; responses are cached for a minute.

MCP

Add the MCP server

Streamable HTTP, no auth. Two tools: search finds an operation and execute runs it. The old tools (get_provider, list_feed and the rest) still answer; they are deprecated and leave these docs on 2027-01-10.

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.

entities.search
Search incidents
entities.get
One entity by id, any type
entities.list
One page of one entity type
feed.read
The items a /feed subscriber gets, as JSON Feed, newest first
rankings.list
Every ranking the site has, with its id, title, the entity type it ranks, its periods
rankings.get
One ranking's rows, ranked
feedback.send
Send a note to the people who run down.guide
stack.check
Which providers a project depends on, and whether any has a problem now
dependency.check
One dependency to the providers behind it and their live state
report.outage
Report that a provider isn't working for you (or for the agent's user) right now
report.affected
Say an existing incident affects you
incident.list
The newest incidents across providers
incident.get
One incident by id: a down.guide id (DWN-…)
provider.list
The provider catalog with live state; q matches names and category narrows it
provider.get
One provider by id: the provider's slug or name, such as github or aws
cascade.list
Upstream outages and the providers that broke with them, newest first; provider names the upstream
cascade.get
One cascade by id: the cascade's slug, such as aws-2026-11-06
leaderboard.get
The Down Index

REST

REST API

Every MCP operation has a REST twin returning the same JSON.

OpenAPI
Get provider
GET /api/v1/providers/<slug>
List feed
GET /api/v1/incidents
Get incident
GET /api/v1/incidents/<id>
Get cascade
GET /api/v1/cascades/<slug>
Search
GET /api/v1/search
Check stack
POST /api/v1/check
Check dependency
GET /api/v1/dependency
Get leaderboard
GET /api/v1/leaderboard
Send feedback
POST /api/v1/feedback
Report outage
POST /api/v1/reports
Report affected
POST /api/v1/reports/affected
Catalog
GET /api/v1/providers
Every provider, one line each
GET /api/v1/status
curl https://down.guide/api/v1/providers/github

Feeds

Feeds and badges

RSS, Atom or JSON Feed: incidents by default, or cascades too, filtered by provider, category, impact or region. Badges show a provider's live state. The subscribe form on the homepage also sends the same selection by email.

https://down.guide/feed?provider=github,vercel&filter=major&format=json
https://down.guide/feed?type=all&provider=aws
[![GitHub status](https://down.guide/badge/github.svg)](https://down.guide/providers/github)

Docs

Docs for agents

Every page also has a markdown copy: add .md to the URL.

llms.txt · llms-full.txt · openapi.json · agent.json

Changelog

Latest changes

Dates are UTC. The full changelog is also JSON and an RSS feed.

Full changelog

ChangedWeb · API · MCP · Feed

Every incident has one headline on every surface

An incident's title is the same headline on the page, the feed, REST, MCP, search, the share card and posts. sourceTitle carries the provider's own title and titleTags lists what the headline dropped.

  • The headline drops the status word, the ticket id and leading bracket groups, and each one stays as a { kind, value } tag.
  • Incidents from the last 90 days are re-derived, so older titles change once.

AddedWeb · API · Feed

The changelog has its own page, JSON and feed

/changelog lists every change as one entry with its date, kind and surfaces. /changelog.json and /changelog.xml (RSS, or ?format=atom and ?format=json) carry the same list.

  • /agents shows the latest five entries and links to the full list.
  • A response that carries a renamed name now sends a Link header to /changelog instead of /agents#changelog.
AddedAPI

Status reports how fresh each source is

GET /api/v1/status carries a freshness block: how many sources down.guide follows, how many it fetched, which ones are failing and when the newest fetch happened.

  • The block has sources_total, sources_read, failed_sources and newest_read_at.
  • Each source that has not been fetched is listed with its pipeline, its error and unread_for_ms.

ChangedWeb · API · MCP · CLI

Every entity type is served the same way on both sites

Every entity type has a page, a REST list and get, rows in search results, the common MCP operations and the common CLI commands, on cve.now and on down.guide. After each deploy a live probe requests every one of them.

  • cve.now and down.guide use the same operation names, so a client written for one works on the other.
ChangedWeb

The developer page moved to /agents

/developers answers 308 to /agents, which holds the MCP setup, the REST reference, the feeds and the changelog.