Compare the status, incidents stats and history between Semaphore 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. Implementing the retry command should help mitigate the issue: https://docs.semaphore.io/reference/toolbox#retry
Operations towards the AWS US-East region might present some slowness. We are currently investigating this issue.
We are currently investigating this issue. Operations towards the AWS US-East region might present some slowness.
We are continuing to experience elevated latency in APAC and EU.
We had an incident overnight that entailed several server outages affecting APAC and EU users. The impact has been latency in recent build times for those users. We have resolved the issue and are ...
We received reports from EU customers of elevated latency and have resolved the cause. We will be managing workloads to ensure standard processing times for all new builds, and scaling resources to...
14-day free trial · No credit card required · No code required