Minor Service Outage
The Anthropic api.anthropic.com component had degraded performance. CircleCI reports that the incident is resolved and lasted 24 minutes.
State
Resolved
Started
Lasted
24 min
Worst impact
Degraded
Timeline
2 updatesComponents degraded
24 min 100%
Updates
Times in UTCAs posted by CircleCI
Affected components
1CircleCI in the last 90 days
Full historyIncidents in 90 days
39
Days with an incident
28
Median duration
1 h 13 min
This incident
67% shorter than the median
Other CircleCI incidents
All incidentsCircleCI·Delays and intermittent failures running Smarter Testing
Smarter Testing had delays and intermittent failures that affected Docker, Machine, macOS, and Windows jobs. CircleCI reports that the incident is resolved and that the outage lasted 2 hours and 48 minutes.
CircleCI·Minor Service Outage
CircleCI reports degraded service on api.anthropic.com. CircleCI reports that the incident is resolved and that it lasted 3 minutes.
CircleCI·Partially Degraded Service
CircleCI reports a partially degraded service that affects GitHub Pull Requests. CircleCI resolved this incident. It lasted 4 hours and 6 minutes.
CircleCI·Partially Degraded Service
CircleCI reported degraded service for GitHub Pull Requests. CircleCI resolved the issue. The outage lasted 3 minutes.
CircleCI·Minor Service Outage
CircleCI reports degraded service on Anthropic api.anthropic.com. CircleCI resolved the incident after 75 minutes.
Follow CircleCI
Your coding agent knows when CircleCI is down, and tells you when a failure is theirs, not yours. You can also get CircleCI incidents in a feed reader or in Slack.
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 "circleci" and tell me if CircleCI 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.
https://outages.live/feed.xml?providers=circleci/feed subscribe https://outages.live/feed.xml?providers=circleciFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane