Compare the status, incidents stats and history between Travis CI and Coveralls
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.
We are continuing to experience 504 Timeouts and 503 Heavy Load errors originating at our load balancers. We believe it is a continuation of recent issues overnight, described here: https://status....
We experienced some general performance issues last night that continued into early morning, but, this morning, should only be affecting a small group of repos: The group of affected repos should ...
We are experiencing degraded performance on some of our production servers. We have scaled infrastructure to address the issue and bring down background job queues. Build times should be back to no...
Try it out! How much time you'll save your team, by having the outages information close to them?