Compare the status, incidents stats and history between Semaphore and Circle 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.
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.
There are currently issues creating and modifying projects using the Project Settings UI. We have identified the cause and are working on a remediation now. We appreciate your patience whilst we w...
At present customers running Docker containers cannot use /mnt/ramdisk. Customers will need to modify their configuration to use the filesystem instead. This has occurred in order to update the Do...
We are experiencing delays starting jobs for M1 and M4 medium and large resource classes. Running jobs on these resource classes will also experience delays due to degraded network performance.
14-day free trial · No credit card required · No code required