checked Sep 11, 2026 2:51 PM UTC · CircleCI's official status page
CircleCI is up and running.
All components operational
Statusfield watches CircleCI alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
16 reports published by CircleCI in the last 30 days
When CircleCI breaks, it is typically resolved in 1h 2m — median across 95 resolved incidents over 90 days.
resolvedSep 10 · 20:26 UTC
This incident has been resolved. A small number of customers who created pipelines between 18:53 UTC and 19:24 UTC that contained config using deprecated config syntax will have seen their build-type jobs fail to start. Customers whose jobs or pipelines failed may rerun them.
Reported by CircleCI on their status page.
resolvedSep 10 · 19:00 UTC
A small number of customers may see errors or be unable to load the pipelines page for projects with deprecated-config warnings, when using the classic pipelines view. Customers on the new pipelines view are not affected. We’ve identified the cause and deployed a fix.
Reported by CircleCI on their status page.
resolvedSep 4 · 16:55 UTC
We've seen no further impact to queue times and everything has returned to normal. We appreciate your patience while we worked to resolve and monitor this issue.
Reported by CircleCI on their status page.
resolvedAug 26 · 16:10 UTC
This incident has been resolved.
Reported by CircleCI on their status page.
resolvedAug 25 · 20:00 UTC
Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.
Reported by CircleCI on their status page.
ResolvedAug 25 · 20:00 UTC
Between 19:49 UTC and 21:07 UTC on August 25, 2026, customers attempting to log in to CircleCI using GitHub were unable to sign in, and received an error from GitHub stating the callback URL was invalid. Customers who were already logged in were not affected. The issue has been resolved and GitHub login is functioning normally. We thank you for your patience while our team worked on implementing a fix.
Reported by CircleCI on their status page.
resolvedAug 17 · 21:37 UTC
Insights data is good once more. Thank you for your patience.
Reported by CircleCI on their status page.
ResolvedAug 17 · 21:37 UTC
Insights data is good once more. Thank you for your patience.
Reported by CircleCI on their status page.
resolvedAug 17 · 19:05 UTC
GitHub's APIs appear to be operating normally.
Reported by CircleCI on their status page.
ResolvedAug 17 · 19:05 UTC
GitHub's APIs appear to be operating normally.
Reported by CircleCI on their status page.
ResolvedAug 15 · 17:00 UTC
Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced.Some customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC.This has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.
Reported by CircleCI on their status page.
resolvedAug 15 · 17:00 UTC
Following planned maintenance that ended at 13:00 UTC on August 15, some impact to job processing continued for approximately 30 minutes beyond the window we announced. Some customers continued to see delays in jobs starting, along with a small number of jobs failing with infrastructure errors, until approximately 13:30 UTC. This has been resolved and job processing has returned to normal. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix and apologize for any inconvenience the extended impact may have caused.
Reported by CircleCI on their status page.
CompletedAug 15 · 13:00 UTC
The scheduled maintenance has been completed.
Reported by CircleCI on their status page.
CompletedAug 14 · 05:00 UTC
The scheduled maintenance has been completed.
Reported by CircleCI on their status page.
resolvedAug 12 · 16:43 UTC
The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.
Reported by CircleCI on their status page.
ResolvedAug 12 · 16:43 UTC
The issue impacting customers who use GitHub as their VCS while GitHub was undergoing a service degradation (https://www.githubstatus.com/incidents/76t89hbfb09h) has now been resolved. GitHub has resolved the underlying issue and the affected functionality has returned to normal. We thank you for your patience.
Reported by CircleCI on their status page.
