Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for CircleCI and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for CircleCI.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Artifacts | Active |
Billing & Account | Active |
CircleCI Insights | Active |
CircleCI Releases | Active |
CircleCI UI | Active |
CircleCI Webhooks | Active |
Docker Jobs | Active |
Machine Jobs | Active |
macOS Jobs | Active |
Notifications & Status Updates | Active |
Pipelines & Workflows | Active |
Runner | Active |
Windows Jobs | Active |
CircleCI Dependencies | Active |
AWS | Active |
Google Cloud Platform Google Cloud DNS | Active |
Google Cloud Platform Google Cloud Networking | Active |
Google Cloud Platform Google Cloud Storage | Active |
Google Cloud Platform Google Compute Engine | Active |
mailgun API | Active |
mailgun Outbound Delivery | Active |
mailgun SMTP | Active |
OpenAI | Active |
Upstream Services | Active |
Atlassian Bitbucket API | Active |
Atlassian Bitbucket Source downloads | Active |
Atlassian Bitbucket SSH | Active |
Atlassian Bitbucket Webhooks | Active |
Docker Authentication | Active |
Docker Hub | Active |
Docker Registry | Active |
GitHub API Requests | Active |
GitHub Git Operations | Active |
GitHub Packages | Active |
GitHub Pull Requests | Active |
GitHub Webhooks | Active |
GitLab | Active |
View the latest incidents for CircleCI and check for official updates:
Description: From 16:02 UTC to 16:16 UTC steps that invoke the "circleci tests run" command will have failed with a 404. We have fixed the underlying issue and any jobs that used this command will need to be rerun. This same error message occurred from 16:40 UTC to 16:43 UTC. All jobs that experienced this issue will need to be rerun.
Status: Resolved
Impact: None | Started At: July 16, 2024, 4 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 3, 2024, 8:07 a.m.
Description: The issue affecting setup of new projects has now been resolved and there is no ongoing impact to customers.
Status: Resolved
Impact: Minor | Started At: July 2, 2024, 10:53 p.m.
Description: \*\*Summary and Impact:\*\* On July 2, 2024, at 07:34 UTC, a deployment change in production using the MicroFrontends \(MFEs\) migration Ingress guide caused Kong routing to break for the [circleci.com](http://circleci.com) host. This led to the unavailability of APIs and UI. The issue was resolved by reverting the change in web-ui-v1, restoring Kong routing. \*\*Customer Impact Analysis:\*\* The incident had a major impact as customers were unable to access any UI or ingest pipelines. An estimated 16.5k pipelines were affected based on traffic data. \*\*Background:\*\* The incident was related to merging MicroFrontends \(MFEs\) in the web-ui-consolidated monorepo. A change in Kong routing led to the breakdown of APIs and UI functionality. \*\*What Happened:\*\* Issues arose due to how Kong handles route priorities, leading to unexpected behavior. The incident was exacerbated by a bug in the Kong router, impacting multiple routes. \*\*Lessons Learned and Future Steps:\*\* * Conduct incident bot testing and improve incident response protocols. * Investigate route priorities and upgrade Kong for better routing. * Enhance internal documentation on route priorities to prevent similar incidents. \*\*Timeline:\*\* * 07:35:46 UTC: Customer Impact Start * 07:39:53 UTC: Initial investigation initiated * 08:05:45 UTC: Helm Rollback applied, issue resolved * 08:06:00 UTC: Customer Impact End * 08:38:00 UTC: Incident End We are committed to improving our systems and processes to prevent such incidents in the future
Status: Postmortem
Impact: Critical | Started At: July 2, 2024, 8:09 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 1, 2024, 9:49 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.