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.
The web UI will fail to load for some customers. We have identified the cause of the issue and are working towards a resolution.
We have received reports of slow checkout/clones of repositories from GitHub. This is not impacting all checkouts and the operations eventually succeed.
We are currently seeing an issue with an upstream provider that is causing some users to experience slow checkout times in their builds.
We have observed some issues with our Mac build process. Our team is investigating these issues and we will be providing further updates as more information becomes available
Issues with branch/tag based builds reported since Nov-9 have been confirmed to be on Travis CI side. We have identified the reason and confirmed it's due to GitHub push event handling on Travis CI...
We received information on issues with data synchronization with GitHub since Nov/1st. We have identified reason and are working on restoring system to normal operation.
How much time you'll save your team, by having the outages information close to them?
14-day free trial · No credit card required · Cancel anytime