Compare the status, incidents stats and history between Travis CI and Circle CI
Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.
We are currently investigating the issue. The symptoms are that either adding new repository or installing Travis CI GitHub App from scratch results in repositories not being activated and builds c...
We have identified the issue where some of the builds are not being triggered and got an undetailed error when they are triggered.
The issue has been identified and a fix is being implemented.
On January 4, 2023, we alerted customers of a security incident and recommended customers rotate all secrets and environment variables stored in CircleCI. Please refer to the following blog post fo...
We are currently seeing failures in our UI due to changes related to our ongoing security investigation. We have already identified the cause and expect to restore service shortly.
We are currently investigating an issue where new triggers set for GitLab projects are not triggering pipelines.
Try it out! How much time you'll save your team, by having the outages information close to them?