Compare the status, incidents stats and history between Circle CI and Travis 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 seeing longer queue times for some jobs. Users may see a 10-15 minute delay for Linux machine jobs and remote docker jobs
CircleCI is currently seeing issues with GitLab webhooks causing builds from GitLab to not trigger. We are investigating the cause of this issue.
We are seeing a delay in the execution of Docker jobs. Customers would see delays in the "Preparing Environment" steps. We have identified the cause and are working towards resolving the issue.
Users utilizing Custom SSH Key in Travis CI private repository settings may experience build errors or warnings on git checkout. This is due main SSH keys being updated by GitHub (see https://githu...
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.
Try it out! How much time you'll save your team, by having the outages information close to them?