Circle CI vs. Semaphore

Compare the status, incidents stats and history between Circle CI and Semaphore

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.

Circle CI

Circle CI current official status is Operational

Statistics

1
Incidents in the last 7 days
5
Incidents in the last 30 days
11
Incidents in the last 90 days

Latest incidents

Resolved Some pipelines failed to be created

A fix has been implemented and we are monitoring the results. Customers should re-trigger impacted pipelines, either in the UI or by re-pushing the work to the code repository.

Resolved Customers may be seeing delays with their workflows starting and may notice issues viewing their workflows through our UI

We are currently investigating this issue. You can still view pipelines for a specific project in the UI.

Resolved Delayed Status checks and outbound webhooks

Our engineers are currently investigating an issue that may have an impact on Status checks and outbound webhooks. We will provide further updates as more information becomes available.

Semaphore

Semaphore current official status is Operational

Statistics

1
Incidents in the last 7 days
3
Incidents in the last 30 days
5
Incidents in the last 90 days

Latest incidents

Resolved Delays in job processing on Semaphore 2.0

We are currently investigating this issue.

Resolved Issues with GitHub Status checks on PR builds

We are currently investigating this issue.

Resolved Elevated error rates on Semaphore

We are currently investigating this issue.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required