Semaphore CI Outage History
Uptime record, past incidents, and downtime history for Semaphore CI.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 80% | 15 | 3 |
| July 2026 | 74.2% | 31 | 8 |
| June 2026 | 76.7% | 30 | 7 |
| May 2026 | 73.3% | 15 | 4 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
May 17
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Bitbucket integration may currently be experiencing issues
Started: Aug 4, 10:38 AM
monitoring
A fix has been implemented and we are monitoring the results.
Aug 4, 11:30 AM
identified
The issue has been identified and a fix is being implemented.
Aug 4, 10:38 AM
July 2026
Delays in job processing
Started: Jul 23, 12:35 AM
monitoring
A fix has been implemented and we have observed an improvement in job processing. We are continuing to monitor the situation.
Jul 23, 2:00 AM
identified
The issue has been identified and a fix is being implemented.
Jul 23, 1:25 AM
investigating
We are continuing to investigate this issue.
Jul 23, 1:03 AM
investigating
We are currently investigating this issue.
Jul 23, 12:35 AM
Some jobs may have issues authenticating with GitHub
Started: Jul 21, 8:36 AM
monitoring
GitHub confirmed that the incident on their end has been resolved, and services should now be returning to normal.
We are continuing to monitor the situation. You can review the GitHub update here:
https://www.githubstatus.com/incidents/g40zcbvchny4
Jul 21, 12:18 PM
monitoring
We are continuing to monitor the situation, and you can follow the current GitHub incident at the following link:
https://www.githubstatus.com/incidents/g40zcbvchny4
Jul 21, 10:53 AM
monitoring
Our team is monitoring the situation. If you are affected, please regenerate your deploy key by following the instructions on this page: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key
Jul 21, 9:25 AM
investigating
Our engineering team is still investigating and working on this issue, but as a current workaround, you can regenerate your GitHub deployment key.
You can find the instructions on how to do that here: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key
Jul 21, 9:06 AM
investigating
As a workaround to get more consistent builds during this time, please try adding the --use-cache flag to your checkout command.
Read more about it here: https://docs.semaphore.io/reference/toolbox#cache-full-clone
Jul 21, 8:49 AM
investigating
We are currently investigating this issue.
Jul 21, 8:36 AM
Some features may currently be unresponsive
Started: Jul 17, 10:32 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 17, 10:51 AM
investigating
We are currently investigating this issue.
Jul 17, 10:32 AM
Delays in job processing
Started: Jul 17, 12:21 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jul 17, 12:43 AM
investigating
We are currently investigating this issue.
Jul 17, 12:21 AM
June 2026
Elevated error rates
Started: Jun 24, 9:01 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 24, 9:16 PM
identified
The issue has been identified and a fix is being implemented.
Jun 24, 9:07 PM
investigating
We are currently investigating this issue.
Jun 24, 9:01 PM
Elevated Error Rates
Started: Jun 10, 3:12 PM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 10, 4:14 PM
identified
The issue has been identified, and our team is implementing a fix.
Jun 10, 3:20 PM
identified
We're experiencing an elevated level of 500's errors and are currently looking into the issue.
Jun 10, 3:12 PM
May 2026
Delays when checking out GitHub repos via SSH
Started: May 20, 8:44 AM
monitoring
A fix has been implemented, and everything should be back to normal. The previously shared snippets can be removed.
May 20, 3:02 PM
identified
We identified slow GitHub operations related to problems with the network, and we deployed a fix to re-route those operations to a healthier server. Some HTTPS operations started to fail because of that. To disable the fix, you should use the command:
sudo sed -i 's/^\([0-9].*github\.com\)/#\1/' /etc/hosts
And to re-enable, you can use:
sudo sed -i 's/^#\([0-9].*github\.com\)/\1/' /etc/hosts
May 20, 1:59 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 20, 12:48 PM
identified
We identified slow communication between Semaphore jobs and GitHub. We are continuing to work with our upstream provider to resolve this. For impacted jobs, please replace the normal checkout command with the following:
retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout'"
And afterwards, use cd to change the directory to the cloned repository (replace with your project).
May 20, 8:44 AM
Delays when checking out GitHub repos via SSH
Started: May 19, 10:00 AM
monitoring
We are not currently seeing timeouts related to slow connections. Our team is continuing to monitor the situation to confirm that service has fully returned to normal.
May 19, 3:10 PM
identified
We identified that the issue is slow communication between our jobs and GitHub. We are currently working with our upstream provider to to resolve this. For impacted jobs, please replace the normal checkout command with the following:
retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout'"
And afterwards, use cd <dir> to change the directory to the cloned repository (replace <dir> with your project).
May 19, 11:18 AM
investigating
We are continuing to investigate this issue.
May 19, 10:38 AM
investigating
We are currently investigating this issue.
May 19, 10:00 AM