Semaphore Outage History
Semaphore is up right nowSemaphore had 28 outages in the last 2 years totaling 98h 53m of downtime — averaging 1.2 incidents per month.
There were 28 Semaphore outages since June 10, 2025 totaling 98h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Delays in Job Processing
Timeline · 5 updates
- investigating Aug 27, 2026, 08:09 PM UTC
We are currently investigating this issue.
- investigating Aug 27, 2026, 08:11 PM UTC
We are continuing to investigate this issue.
- identified Aug 27, 2026, 08:26 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 27, 2026, 08:35 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 27, 2026, 09:01 PM UTC
This incident has been resolved.
Platform Outage
Timeline · 4 updates
- identified Aug 27, 2026, 06:43 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 27, 2026, 07:00 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 27, 2026, 07:15 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 27, 2026, 07:30 PM UTC
This incident has been resolved.
Degraded performance on r1-standard machines
Timeline · 7 updates
- investigating Aug 25, 2026, 08:35 AM UTC
We are currently investigating this issue.
- identified Aug 25, 2026, 08:44 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 25, 2026, 09:19 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 25, 2026, 12:57 PM UTC
We are continuing to monitor for any further issues.
- identified Aug 25, 2026, 02:00 PM UTC
We have observed continued impact while monitoring. The issue remains identified, and our team is working on a resolution.
- identified Aug 25, 2026, 02:17 PM UTC
We are continuing to work on a fix for this issue.
- resolved Aug 25, 2026, 02:47 PM UTC
This incident has been resolved.
Issues with Bitbucket integration
Timeline · 5 updates
- investigating Aug 21, 2026, 07:14 PM UTC
We are currently investigating this issue.
- identified Aug 21, 2026, 07:26 PM UTC
The issue has been identified and a fix is being implemented.
- identified Aug 21, 2026, 08:03 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 21, 2026, 08:27 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 21, 2026, 08:47 PM UTC
This incident has been resolved.
Delays in job processing - F1 machines
Timeline · 8 updates
- investigating Aug 18, 2026, 03:07 PM UTC
We are currently investigating this issue.
- investigating Aug 18, 2026, 03:15 PM UTC
Jobs configured to run on F1 machines may take longer than usual to start.
- identified Aug 18, 2026, 03:18 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 18, 2026, 03:24 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Aug 18, 2026, 03:28 PM UTC
The issue is still ongoing, and the engineering team is actively working on a fix.
- identified Aug 18, 2026, 04:28 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 18, 2026, 05:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 18, 2026, 05:47 PM UTC
This incident has been resolved.
Bitbucket integration may currently be experiencing issues
Timeline · 3 updates
- identified Aug 04, 2026, 10:38 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 04, 2026, 11:30 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 04, 2026, 12:04 PM UTC
This incident has been resolved.
Some jobs may have issues authenticating with GitHub
Timeline · 7 updates
- investigating Jul 21, 2026, 08:36 AM UTC
We are currently investigating this issue.
- investigating Jul 21, 2026, 08:49 AM UTC
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
- investigating Jul 21, 2026, 09:06 AM UTC
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
- monitoring Jul 21, 2026, 09:25 AM UTC
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
- monitoring Jul 21, 2026, 10:53 AM UTC
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
- monitoring Jul 21, 2026, 12:18 PM UTC
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
- resolved Jul 21, 2026, 01:46 PM UTC
GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4
Some features may currently be unresponsive
Timeline · 3 updates
- investigating Jul 17, 2026, 10:32 AM UTC
We are currently investigating this issue.
- monitoring Jul 17, 2026, 10:51 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 17, 2026, 01:25 PM UTC
This incident has been resolved.
Elevated error rates
Timeline · 4 updates
- investigating Jun 24, 2026, 09:01 PM UTC
We are currently investigating this issue.
- identified Jun 24, 2026, 09:07 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 24, 2026, 09:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 24, 2026, 09:26 PM UTC
This incident has been resolved.
Elevated Error Rates
Timeline · 4 updates
- identified Jun 10, 2026, 03:12 PM UTC
We're experiencing an elevated level of 500's errors and are currently looking into the issue.
- identified Jun 10, 2026, 03:20 PM UTC
The issue has been identified, and our team is implementing a fix.
- monitoring Jun 10, 2026, 04:14 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2026, 04:22 PM UTC
This incident has been resolved.
Delays when checking out GitHub repos via SSH
Timeline · 5 updates
- identified May 20, 2026, 08:44 AM UTC
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).
- monitoring May 20, 2026, 12:48 PM UTC
A fix has been implemented and we are monitoring the results.
- identified May 20, 2026, 01:59 PM UTC
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
- monitoring May 20, 2026, 03:02 PM UTC
A fix has been implemented, and everything should be back to normal. The previously shared snippets can be removed.
- resolved May 20, 2026, 03:32 PM UTC
This incident has been resolved.
Jobs Not Starting and Processing Delays
Timeline · 6 updates
- investigating Feb 24, 2026, 08:49 AM UTC
We are currently investigating this issue.
- investigating Feb 24, 2026, 09:06 AM UTC
We are continuing to investigate this issue.
- investigating Feb 24, 2026, 09:34 AM UTC
We are continuing to investigate job start failures and processing delays. We will continue to update while investigating this.
- identified Feb 24, 2026, 09:54 AM UTC
The issue has been identified and we are working on a fix. We will provide our next update within 30 minutes or sooner if things change. We thank you for your patience while we continue to work to resolve this issue.
- monitoring Feb 24, 2026, 10:05 AM UTC
A fix has been implemented and we are monitoring the results. We will provide our next update within 30 minutes or sooner if things change.
- resolved Feb 24, 2026, 10:32 AM UTC
This incident has been resolved.
Delivering webhooks delays between Github and Semaphore
Timeline · 4 updates
- investigating Feb 03, 2026, 03:46 PM UTC
We are currently investigating this issue.
- identified Feb 03, 2026, 05:34 PM UTC
Webhook delivery delays between GitHub and Semaphore appear to be caused by degraded performance on GitHub’s side. GitHub is currently reporting an active incident that appears related. We are monitoring the situation closely and will provide updates as GitHub resolves the issue.
- monitoring Feb 03, 2026, 07:11 PM UTC
GitHub has posted an update indicating recovery of the aforementioned issue. We continue monitoring Semaphore closely as things stabilize. (GitHub Status: https://www.githubstatus.com/incidents/f314nlctbfs5)
- resolved Feb 03, 2026, 07:50 PM UTC
This incident has been resolved.
Delays in job processing on Semaphore
Timeline · 5 updates
- identified Jan 27, 2026, 03:34 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jan 27, 2026, 04:35 PM UTC
We are continuing to work on a fix for this issue.
- identified Jan 27, 2026, 05:36 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jan 27, 2026, 06:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 27, 2026, 07:10 PM UTC
This incident has been resolved.
Network connectivity issues towards us-east
Timeline · 5 updates
- investigating Nov 12, 2025, 02:55 PM UTC
We are currently investigating the issue. Implementing the retry command should help mitigate the issue: https://docs.semaphore.io/reference/toolbox#retry
- investigating Nov 12, 2025, 03:28 PM UTC
We are continuing to investigate this issue.
- identified Nov 12, 2025, 04:24 PM UTC
We’ve identified that these issues are being caused by inconsistent network routing between Europe and the United States on upstream providers. Semaphore’s systems remain healthy, but affected routes can cause slower file transfer and occasional connection timeouts.
- monitoring Nov 12, 2025, 05:34 PM UTC
The connection seems stable and we keep monitoring it.
- resolved Nov 12, 2025, 06:10 PM UTC
This incident has been resolved.
Network congestion on route to AWS ECR us-east region
Timeline · 18 updates
Slow job processing
Timeline · 8 updates
- identified Oct 29, 2025, 11:38 AM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 29, 2025, 12:24 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 29, 2025, 12:53 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 29, 2025, 01:30 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 29, 2025, 02:22 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 29, 2025, 03:22 PM UTC
We are continuing to monitor for any further issues.
- monitoring Oct 29, 2025, 03:58 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 29, 2025, 04:28 PM UTC
This incident has been resolved.
Delays in job completion on Semaphore
Timeline · 4 updates
- investigating Oct 21, 2025, 08:58 AM UTC
We are currently investigating this issue.
- identified Oct 21, 2025, 09:35 AM UTC
The issue has been identified, and we are working on a fix.
- monitoring Oct 21, 2025, 09:44 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 21, 2025, 09:58 AM UTC
This incident has been resolved.
Docker Hub outage affecting image push/pulls in Semaphore
Timeline · 12 updates
Slow job processing on e2 machine types
Timeline · 8 updates
- investigating Oct 02, 2025, 06:48 PM UTC
We are currently investigating this issue.
- investigating Oct 02, 2025, 07:27 PM UTC
We are continuing investigating this issue.
- identified Oct 02, 2025, 08:00 PM UTC
The issue has been identified and a fix is being implemented.
- identified Oct 02, 2025, 08:46 PM UTC
We are continuing to work on a fix for this issue.
- identified Oct 02, 2025, 09:18 PM UTC
We're finalizing a fix for this issue.
- identified Oct 02, 2025, 09:52 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 02, 2025, 09:56 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Oct 02, 2025, 10:26 PM UTC
This incident has been resolved.
Slow job processing on C1 machine types
Timeline · 4 updates
- identified Sep 17, 2025, 01:02 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 17, 2025, 01:34 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Sep 17, 2025, 01:50 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 17, 2025, 02:11 AM UTC
This incident has been resolved.
New project initialization issues
Timeline · 6 updates
- investigating Sep 12, 2025, 09:41 AM UTC
We are currently investigating this issue.
- investigating Sep 12, 2025, 10:09 AM UTC
We are continuing to investigate this issue.
- identified Sep 12, 2025, 10:27 AM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 12, 2025, 11:24 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Sep 12, 2025, 11:47 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 12, 2025, 12:04 PM UTC
This incident has been resolved.
Job processing delays due to connectivity issues with GitHub
Timeline · 3 updates
- investigating Sep 04, 2025, 05:12 PM UTC
We are currently investigating this issue.
- monitoring Sep 04, 2025, 05:52 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 04, 2025, 06:35 PM UTC
This incident has been resolved.
"Plans & Billing" page unavailable
Timeline · 4 updates
- identified Aug 19, 2025, 11:01 AM UTC
The issue has been identified and a fix is being implemented.
- identified Aug 19, 2025, 11:36 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Aug 19, 2025, 11:57 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 19, 2025, 12:13 PM UTC
This incident has been resolved.