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 currently investigating reports that some GitLab pipelines are not running for some of our users
We are currently investigating reports of slow UI and delayed job starts.
Starting at 15:14 UTC, we are seeing a long queue time for docker jobs that use the x.large resource class. We are investigating the cause of this issue.
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.
The main page at https://travis-ci.com is down. Your builds are still executed. We're reviewing the main site case, it may remain inactive for a full day or so. The API and https://app.travis-ci.co...
Try it out! How much time you'll save your team, by having the outages information close to them?