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.
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.
After a recent release, we have received reports of `pull_request` builds that have suddenly dropped in coverage with no change in CI setup. Specifically, these builds have had several parallel jo...
We are investigating and trying to resolve an incident that seems related to a previous incident, now resolve, here: https://status.coveralls.io/incidents/pgcdqr7r4lgj We believe that some recentl...
We are experiencing elevated traffic from a couple of sources that has been enough to affect some other repos in queue. While we are addressing this right now, performance may be slightly degrade...
Try it out! How much time you'll save your team, by having the outages information close to them?