Compare the status, incidents stats and history between Circle 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 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.
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?