Semaphore Outage History

Semaphore is up right now

Semaphore had 29 outages in the last 2 years totaling 119h 46m of downtime — averaging 1.2 incidents per month.

There were 29 Semaphore outages since June 30, 2025 totaling 119h 46m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.semaphoreci.com

Minor October 14, 2026

Delays in job processing

Detected by Pingoru
Oct 14, 2026, 03:10 PM UTC
Resolved
Oct 14, 2026, 05:17 PM UTC
Duration
2h 7m
Affected: Semaphore
Timeline · 5 updates
  1. investigating Oct 14, 2026, 03:10 PM UTC

    Jobs are currently experiencing delays during initialization. We are investigating the issue and will share updates as we have more information.

  2. identified Oct 14, 2026, 03:55 PM UTC

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

  3. monitoring Oct 14, 2026, 04:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Oct 14, 2026, 05:09 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 14, 2026, 05:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 17, 2026

Intermittent cache connection errors

Detected by Pingoru
Sep 17, 2026, 01:33 PM UTC
Resolved
Sep 17, 2026, 02:12 PM UTC
Duration
38m
Affected: Semaphore
Timeline · 4 updates
  1. investigating Sep 17, 2026, 01:33 PM UTC

    We are currently investigating this issue.

  2. identified Sep 17, 2026, 01:52 PM UTC

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

  3. monitoring Sep 17, 2026, 01:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 17, 2026, 02:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 27, 2026

Delays in Job Processing

Detected by Pingoru
Aug 27, 2026, 08:09 PM UTC
Resolved
Aug 27, 2026, 09:01 PM UTC
Duration
52m
Affected: Semaphore
Timeline · 5 updates
  1. investigating Aug 27, 2026, 08:09 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 27, 2026, 08:11 PM UTC

    We are continuing to investigate this issue.

  3. identified Aug 27, 2026, 08:26 PM UTC

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

  4. monitoring Aug 27, 2026, 08:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 27, 2026, 09:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 27, 2026

Platform Outage

Detected by Pingoru
Aug 27, 2026, 06:43 PM UTC
Resolved
Aug 27, 2026, 07:30 PM UTC
Duration
47m
Affected: Semaphore
Timeline · 4 updates
  1. identified Aug 27, 2026, 06:43 PM UTC

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

  2. monitoring Aug 27, 2026, 07:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Aug 27, 2026, 07:15 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Aug 27, 2026, 07:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026

Degraded performance on r1-standard machines

Detected by Pingoru
Aug 25, 2026, 08:35 AM UTC
Resolved
Aug 25, 2026, 02:47 PM UTC
Duration
6h 11m
Affected: Semaphore
Timeline · 7 updates
  1. investigating Aug 25, 2026, 08:35 AM UTC

    We are currently investigating this issue.

  2. identified Aug 25, 2026, 08:44 AM UTC

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

  3. monitoring Aug 25, 2026, 09:19 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Aug 25, 2026, 12:57 PM UTC

    We are continuing to monitor for any further issues.

  5. 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.

  6. identified Aug 25, 2026, 02:17 PM UTC

    We are continuing to work on a fix for this issue.

  7. resolved Aug 25, 2026, 02:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 21, 2026

Issues with Bitbucket integration

Detected by Pingoru
Aug 21, 2026, 07:14 PM UTC
Resolved
Aug 21, 2026, 08:47 PM UTC
Duration
1h 33m
Affected: Semaphore
Timeline · 5 updates
  1. investigating Aug 21, 2026, 07:14 PM UTC

    We are currently investigating this issue.

  2. identified Aug 21, 2026, 07:26 PM UTC

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

  3. identified Aug 21, 2026, 08:03 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Aug 21, 2026, 08:27 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Aug 21, 2026, 08:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 18, 2026

Delays in job processing - F1 machines

Detected by Pingoru
Aug 18, 2026, 03:07 PM UTC
Resolved
Aug 18, 2026, 05:47 PM UTC
Duration
2h 40m
Affected: Semaphore
Timeline · 8 updates
  1. investigating Aug 18, 2026, 03:07 PM UTC

    We are currently investigating this issue.

  2. investigating Aug 18, 2026, 03:15 PM UTC

    Jobs configured to run on F1 machines may take longer than usual to start.

  3. identified Aug 18, 2026, 03:18 PM UTC

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

  4. monitoring Aug 18, 2026, 03:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. identified Aug 18, 2026, 03:28 PM UTC

    The issue is still ongoing, and the engineering team is actively working on a fix.

  6. identified Aug 18, 2026, 04:28 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Aug 18, 2026, 05:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Aug 18, 2026, 05:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 4, 2026

Bitbucket integration may currently be experiencing issues

Detected by Pingoru
Aug 04, 2026, 10:38 AM UTC
Resolved
Aug 04, 2026, 12:04 PM UTC
Duration
1h 25m
Affected: Semaphore
Timeline · 3 updates
  1. identified Aug 04, 2026, 10:38 AM UTC

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

  2. monitoring Aug 04, 2026, 11:30 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 04, 2026, 12:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 21, 2026

Some jobs may have issues authenticating with GitHub

Detected by Pingoru
Jul 21, 2026, 08:36 AM UTC
Resolved
Jul 21, 2026, 01:46 PM UTC
Duration
5h 10m
Affected: Semaphore
Timeline · 7 updates
  1. investigating Jul 21, 2026, 08:36 AM UTC

    We are currently investigating this issue.

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

Read the full incident report →

Major July 17, 2026

Some features may currently be unresponsive

Detected by Pingoru
Jul 17, 2026, 10:32 AM UTC
Resolved
Jul 17, 2026, 01:25 PM UTC
Duration
2h 53m
Affected: Semaphore
Timeline · 3 updates
  1. investigating Jul 17, 2026, 10:32 AM UTC

    We are currently investigating this issue.

  2. monitoring Jul 17, 2026, 10:51 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 17, 2026, 01:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 24, 2026

Elevated error rates

Detected by Pingoru
Jun 24, 2026, 09:01 PM UTC
Resolved
Jun 24, 2026, 09:26 PM UTC
Duration
24m
Affected: Semaphore
Timeline · 4 updates
  1. investigating Jun 24, 2026, 09:01 PM UTC

    We are currently investigating this issue.

  2. identified Jun 24, 2026, 09:07 PM UTC

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

  3. monitoring Jun 24, 2026, 09:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 24, 2026, 09:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

Elevated Error Rates

Detected by Pingoru
Jun 10, 2026, 03:12 PM UTC
Resolved
Jun 10, 2026, 04:22 PM UTC
Duration
1h 9m
Affected: Semaphore
Timeline · 4 updates
  1. 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.

  2. identified Jun 10, 2026, 03:20 PM UTC

    The issue has been identified, and our team is implementing a fix.

  3. monitoring Jun 10, 2026, 04:14 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 10, 2026, 04:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 20, 2026

Delays when checking out GitHub repos via SSH

Detected by Pingoru
May 20, 2026, 08:44 AM UTC
Resolved
May 20, 2026, 03:32 PM UTC
Duration
6h 47m
Affected: Semaphore
Timeline · 5 updates
  1. 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).

  2. monitoring May 20, 2026, 12:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. 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

  4. 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.

  5. resolved May 20, 2026, 03:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 24, 2026

Jobs Not Starting and Processing Delays

Detected by Pingoru
Feb 24, 2026, 08:49 AM UTC
Resolved
Feb 24, 2026, 10:32 AM UTC
Duration
1h 42m
Affected: Semaphore
Timeline · 6 updates
  1. investigating Feb 24, 2026, 08:49 AM UTC

    We are currently investigating this issue.

  2. investigating Feb 24, 2026, 09:06 AM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. 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.

  5. 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.

  6. resolved Feb 24, 2026, 10:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 3, 2026

Delivering webhooks delays between Github and Semaphore

Detected by Pingoru
Feb 03, 2026, 03:46 PM UTC
Resolved
Feb 03, 2026, 07:50 PM UTC
Duration
4h 3m
Affected: Semaphore
Timeline · 4 updates
  1. investigating Feb 03, 2026, 03:46 PM UTC

    We are currently investigating this issue.

  2. 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.

  3. 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)

  4. resolved Feb 03, 2026, 07:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 27, 2026

Delays in job processing on Semaphore

Detected by Pingoru
Jan 27, 2026, 03:34 PM UTC
Resolved
Jan 27, 2026, 07:10 PM UTC
Duration
3h 36m
Affected: Semaphore
Timeline · 5 updates
  1. identified Jan 27, 2026, 03:34 PM UTC

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

  2. identified Jan 27, 2026, 04:35 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Jan 27, 2026, 05:36 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jan 27, 2026, 06:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jan 27, 2026, 07:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 12, 2025

Network connectivity issues towards us-east

Detected by Pingoru
Nov 12, 2025, 02:55 PM UTC
Resolved
Nov 12, 2025, 06:10 PM UTC
Duration
3h 14m
Affected: Semaphore
Timeline · 5 updates
  1. 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

  2. investigating Nov 12, 2025, 03:28 PM UTC

    We are continuing to investigate this issue.

  3. 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.

  4. monitoring Nov 12, 2025, 05:34 PM UTC

    The connection seems stable and we keep monitoring it.

  5. resolved Nov 12, 2025, 06:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Slow job processing

Detected by Pingoru
Oct 29, 2025, 11:38 AM UTC
Resolved
Oct 29, 2025, 04:28 PM UTC
Duration
4h 49m
Affected: Semaphore
Timeline · 8 updates
  1. identified Oct 29, 2025, 11:38 AM UTC

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

  2. identified Oct 29, 2025, 12:24 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Oct 29, 2025, 12:53 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Oct 29, 2025, 01:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Oct 29, 2025, 02:22 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Oct 29, 2025, 03:22 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Oct 29, 2025, 03:58 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Oct 29, 2025, 04:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2025

Delays in job completion on Semaphore

Detected by Pingoru
Oct 21, 2025, 08:58 AM UTC
Resolved
Oct 21, 2025, 09:58 AM UTC
Duration
1h
Affected: Semaphore
Timeline · 4 updates
  1. investigating Oct 21, 2025, 08:58 AM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2025, 09:35 AM UTC

    The issue has been identified, and we are working on a fix.

  3. monitoring Oct 21, 2025, 09:44 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 21, 2025, 09:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 2, 2025

Slow job processing on e2 machine types

Detected by Pingoru
Oct 02, 2025, 06:48 PM UTC
Resolved
Oct 02, 2025, 10:26 PM UTC
Duration
3h 38m
Affected: Semaphore
Timeline · 8 updates
  1. investigating Oct 02, 2025, 06:48 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 02, 2025, 07:27 PM UTC

    We are continuing investigating this issue.

  3. identified Oct 02, 2025, 08:00 PM UTC

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

  4. identified Oct 02, 2025, 08:46 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Oct 02, 2025, 09:18 PM UTC

    We're finalizing a fix for this issue.

  6. identified Oct 02, 2025, 09:52 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Oct 02, 2025, 09:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Oct 02, 2025, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 17, 2025

Slow job processing on C1 machine types

Detected by Pingoru
Sep 17, 2025, 01:02 AM UTC
Resolved
Sep 17, 2025, 02:11 AM UTC
Duration
1h 9m
Affected: Semaphore
Timeline · 4 updates
  1. identified Sep 17, 2025, 01:02 AM UTC

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

  2. identified Sep 17, 2025, 01:34 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Sep 17, 2025, 01:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 17, 2025, 02:11 AM UTC

    This incident has been resolved.

Read the full incident report →