CircleCI reported "Partially Degraded Service" on its status page at 2026-11-09 18:24 UTC. CircleCI GitHub Webhooks were degraded. CircleCI reports that the incident is resolved. The outage lasted 24 minutes.

CircleCI lists these components: GitHub Webhooks.

When did the incident start and end?

It started at 2026-11-09 18:24 UTC and ended at 2026-11-09 18:48 UTC. It lasted 24 min.

How do I get alerts for CircleCI?

Subscribe to the CircleCI live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of CircleCI. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CircleCIIncident ·

Partially Degraded Service

ResolvedOfficial update

CircleCI GitHub Webhooks were degraded. CircleCI reports that the incident is resolved. The outage lasted 24 minutes.

State

Resolved

Started

Lasted

24 min

Worst impact

Degraded

Timeline

2 updates

18:2418:3018:3618:4218:48

DegradedUpdate postedTimes in UTC

Components degraded

24 min 100%

Updates

Times in UTC

As posted by CircleCI

Resolved

Components degraded

Affected components

GitHub Webhooks

CircleCI in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 13 min

This incident

67% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

14 h 36 min

median 1 h 13 min

90 days agoToday

Other CircleCI incidents

All incidents

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.

Resolved

CircleCI·Partially Degraded Service

CircleCI reports a partially degraded service for GitHub API Requests. CircleCI resolved the incident. The outage lasted 36 minutes.

Resolved

CircleCI·Partially Degraded Service

CircleCI reports degraded service on Anthropic api.anthropic.com. CircleCI resolved the incident. The incident lasted 24 minutes.

Resolved

CircleCI·Partially Degraded Service

CircleCI reports partially degraded service for GitHub Webhooks. The outage is resolved. It lasted 33 minutes.

Resolved

CircleCI·Minor Service Outage

CircleCI reports degraded GitHub Git Operations, GitHub Pull Requests, and GitHub API Requests. CircleCI reports that the incident is resolved. The incident lasted 99 minutes.

Resolved

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.

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 "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.

RSS

https://outages.live/feed.xml?providers=circleci

Slack

/feed subscribe https://outages.live/feed.xml?providers=circleci

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane