Live

Anthropic

Anthropic is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

50

Days with an incident

42

Median duration

1 h 8 min

Longest incident

6 days

Components

6
claude.ai Operational
90 days ago28 days with an incidentToday
Claude Console (platform.claude.com) Operational
90 days ago12 days with an incidentToday
Claude API (api.anthropic.com) Operational
90 days ago25 days with an incidentToday
Claude Code Operational
90 days ago26 days with an incidentToday
Claude Cowork Operational
90 days ago30 days with an incidentToday
Claude for Government Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Follow Anthropic

Your coding agent knows when Anthropic is down, and tells you when a failure is theirs, not yours. You can also get Anthropic incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "anthropic" and tell me if Anthropic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=anthropic
Slack
/feed subscribe https://outages.live/feed.xml?providers=anthropic

Go from tracking outages to fixing production issues with Polylane.

Try Polylane