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 Minor Outage

Statistics

2
Incidents in the last 7 days
7
Incidents in the last 30 days
17
Incidents in the last 90 days

Latest incidents

Ongoing Job start times for m1.medium, m2pro.medium, and m2pro.large are elevated

Task start times for m1.medium, m2pro.medium, and m2pro.large are elevated and you may experience queueing.

about 1 hour ago Official incident report
Resolved M2Pro.Large resource class jobs delayed

We are currently investigating alerts which indicate that M2Pro Large resources are delayed starting. All jobs will run but customers may experience wait times of 8 to 10 minutes to get machines. T...

Resolved GitLab projects are not building

GitLab jobs are currently not building due to a "Failed to get credential" error. We are currently investigating this issue.

Semaphore

Semaphore current official status is Operational

Statistics

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

Latest incidents

Resolved Job processing delays due to connectivity issues with GitHub

We are currently investigating this issue.

Resolved Network congestion on route to AWS ECR us-east region

We are currently investigating this issue.

Resolved "Plans & Billing" page unavailable

The issue has been identified and a fix is being implemented.

Never again lose time looking in the wrong place

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