Partially Degraded Service
CircleCI reports partially degraded service on GitHub Webhooks. The provider is investigating the incident. The incident started at 20:51 UTC on 11 November 2026.
State
Components degraded
Started
Ongoing for
16 min
Worst impact
Degraded
Timeline
1 updateComponents degraded
16 min 100%
Updates
Times in UTCAs posted by CircleCI
Affected components
1CircleCI in the last 90 days
Full historyIncidents in 90 days
33
Days with an incident
26
Median duration
1 h 19 min
This incident
79% shorter than the median
Other CircleCI incidents
All incidentsCircleCI·Partially Degraded Service
GitHub Webhooks on CircleCI had degraded service. CircleCI reports that the incident is resolved. The outage lasted 6 minutes.
CircleCI·Partially Degraded Service
GitHub Pull Requests on CircleCI had a partial outage. CircleCI reports that the incident is resolved. The outage lasted 2 hours.
CircleCI·Partially Degraded Service
CircleCI GitHub Webhooks were degraded. CircleCI reports that the incident is resolved. The outage lasted 24 minutes.
CircleCI·Partially Degraded Service
CircleCI reports that GitHub Webhooks had degraded performance. CircleCI reports that the incident is resolved. The incident lasted 105 minutes, from 10:03 to 11:48 UTC on 9 November 2026.
CircleCI·Partially Degraded Service
CircleCI reports a partially degraded service for GitHub API Requests. CircleCI resolved the incident. The outage lasted 36 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