Semaphore Outage History

Semaphore is up right now

Pingoru has recorded 59 incidents for Semaphore: 44 in the last 12 months and 21 in the last 90 days.

Source: status.semaphoreci.com

59incidents recorded
44last 12 months
21last 90 days
3 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Semaphore in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 2026213 of 744 (2%)
June 202622 of 720 (0%)
July 2026411 of 744 (1%)
August 2026826 of 744 (3%)
September 2026532 of 720 (4%)
October 2026924 of 744 (3%)
November 202600 of 147 (0%)

Incidents, newest first

Minor October 29, 2026 Delays in Job Processing 1h 25m Semaphore

Started Oct 29, 2026, 10:51 PM UTC· resolved Oct 30, 2026, 12:16 AM UTC

  1. investigating Oct 29, 2026, 10:51 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 29, 2026, 11:18 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 29, 2026, 11:49 PM UTC

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

  4. monitoring Oct 30, 2026, 12:03 AM UTC

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

  5. resolved Oct 30, 2026, 12:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 26, 2026 Delays in Job Processing 3h 14m Semaphore

Started Oct 26, 2026, 11:40 PM UTC· resolved Oct 27, 2026, 02:54 AM UTC

  1. investigating Oct 26, 2026, 11:40 PM UTC

    We are currently investigating this issue.

  2. identified Oct 27, 2026, 12:10 AM UTC

    The issue has been identified, and we are continuing to monitor the situation.

  3. monitoring Oct 27, 2026, 12:36 AM UTC

    We're continuing to monitor the situation closely and will provide further updates.

  4. monitoring Oct 27, 2026, 01:01 AM UTC

    We are starting to see improvements in job processing times, and jobs should be returning to normal.

  5. monitoring Oct 27, 2026, 01:27 AM UTC

    Job processing times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected.

  6. monitoring Oct 27, 2026, 01:39 AM UTC

    We are continuing to monitoring the situation.

  7. identified Oct 27, 2026, 02:05 AM UTC

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

  8. monitoring Oct 27, 2026, 02:35 AM UTC

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

  9. resolved Oct 27, 2026, 02:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 26, 2026 Delays in Job Processing 2h 41m Semaphore

Started Oct 26, 2026, 03:02 PM UTC· resolved Oct 26, 2026, 05:43 PM UTC

  1. investigating Oct 26, 2026, 03:02 PM UTC

    We are currently investigating this issue.

  2. identified Oct 26, 2026, 04:03 PM UTC

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

  3. monitoring Oct 26, 2026, 05:02 PM UTC

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

  4. resolved Oct 26, 2026, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 22, 2026 Delays in Job Processing 2h 15m Semaphore

Started Oct 22, 2026, 03:08 PM UTC· resolved Oct 22, 2026, 05:23 PM UTC

  1. investigating Oct 22, 2026, 03:08 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 22, 2026, 04:03 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 22, 2026, 05:01 PM UTC

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

  4. monitoring Oct 22, 2026, 05:12 PM UTC

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

  5. resolved Oct 22, 2026, 05:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 21, 2026 Delays in Job Processing 3h 46m Semaphore

Started Oct 21, 2026, 02:14 PM UTC· resolved Oct 21, 2026, 06:01 PM UTC

  1. investigating Oct 21, 2026, 02:14 PM UTC

    We are currently investigating this issue.

  2. identified Oct 21, 2026, 02:23 PM UTC

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

  3. monitoring Oct 21, 2026, 02:41 PM UTC

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

  4. monitoring Oct 21, 2026, 03:38 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Oct 21, 2026, 04:33 PM UTC

    We are continuing to monitor for any further issues.

  6. investigating Oct 21, 2026, 05:02 PM UTC

    We are currently investigating this issue.

  7. identified Oct 21, 2026, 05:18 PM UTC

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

  8. monitoring Oct 21, 2026, 05:40 PM UTC

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

  9. resolved Oct 21, 2026, 06:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2026 Delays in jobs scheduling 2h 1m Semaphore

Started Oct 20, 2026, 09:58 PM UTC· resolved Oct 20, 2026, 11:59 PM UTC

  1. identified Oct 20, 2026, 09:58 PM UTC

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

  2. identified Oct 20, 2026, 10:27 PM UTC

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

  3. identified Oct 20, 2026, 10:44 PM UTC

    We're starting to see improvements in job scheduling times, although some delays may still occur. We're continuing to monitor the situation closely and will provide further updates as we make progress.

  4. monitoring Oct 20, 2026, 11:10 PM UTC

    Job scheduling times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected.

  5. monitoring Oct 20, 2026, 11:30 PM UTC

    We are continuing to monitor the situation.

  6. resolved Oct 20, 2026, 11:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 14, 2026 Delays in job processing 2h 7m Semaphore

Started Oct 14, 2026, 03:10 PM UTC· resolved Oct 14, 2026, 05:17 PM UTC

  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 October 13, 2026 Delays in job processing 2h 56m Semaphore

Started Oct 13, 2026, 03:16 PM UTC· resolved Oct 13, 2026, 06:13 PM UTC

  1. investigating Oct 13, 2026, 03:16 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 13, 2026, 03:49 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 13, 2026, 04:47 PM UTC

    We're starting to see improvements in job processing times, although some delays may still occur. We're continuing to monitor the situation closely and will provide further updates as we make progress.

  4. monitoring Oct 13, 2026, 05:43 PM UTC

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

  5. resolved Oct 13, 2026, 06:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 13, 2026 Intermittent network connectivity issues 8h 36m Semaphore

Started Oct 13, 2026, 01:53 PM UTC· resolved Oct 13, 2026, 10:30 PM UTC

  1. investigating Oct 13, 2026, 01:53 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 13, 2026, 02:32 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 13, 2026, 02:40 PM UTC

    The issue has been identified.

  4. identified Oct 13, 2026, 03:42 PM UTC

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

  5. investigating Oct 13, 2026, 04:34 PM UTC

    We identified that the intermittent network connectivity issues are likely related to our infrastructure provider's recent maintenance. Although the maintenance is complete, we're still experiencing intermittent connection interruptions and slow network performance.

  6. investigating Oct 13, 2026, 06:16 PM UTC

    We are continuing to investigate this issue.

  7. identified Oct 13, 2026, 06:31 PM UTC

    Our investigation has identified intermittent connectivity issues between our infrastructure provider’s network and certain Google services. This may affect artifact uploads and downloads, as well as jobs that depend on Google-hosted resources. We’ve gathered diagnostic information and are escalating the issue to our infrastructure provider for further investigation. We’ll continue monitoring the situation and share updates as significant new information becomes available.

  8. monitoring Oct 13, 2026, 09:45 PM UTC

    Network connectivity is returning to normal, and the affected services should no longer be impacted. We will continue monitoring the situation closely. If you continue to experience similar issues, please contact our support team at [email protected].

  9. resolved Oct 13, 2026, 10:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 17, 2026 Delays in job processing 51m Semaphore

Started Sep 17, 2026, 02:17 PM UTC· resolved Sep 17, 2026, 03:09 PM UTC

  1. investigating Sep 17, 2026, 02:17 PM UTC

    We are currently investigating this issue.

  2. identified Sep 17, 2026, 02:29 PM UTC

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

  3. monitoring Sep 17, 2026, 02:47 PM UTC

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

  4. resolved Sep 17, 2026, 03:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 17, 2026 Intermittent cache connection errors 38m Semaphore

Started Sep 17, 2026, 01:33 PM UTC· resolved Sep 17, 2026, 02:12 PM UTC

  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 →

Minor September 15, 2026 Delays in job processing 2h 1m Semaphore

Started Sep 15, 2026, 02:45 PM UTC· resolved Sep 15, 2026, 04:46 PM UTC

  1. investigating Sep 15, 2026, 02:45 PM UTC

    We are currently investigating this issue.

  2. identified Sep 15, 2026, 02:52 PM UTC

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

  3. identified Sep 15, 2026, 03:49 PM UTC

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

  4. monitoring Sep 15, 2026, 04:16 PM UTC

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

  5. resolved Sep 15, 2026, 04:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 2, 2026 Periodic authentication failure with GitHub repositories 1d Semaphore

Started Sep 02, 2026, 04:08 PM UTC· resolved Sep 03, 2026, 04:41 PM UTC

  1. identified Sep 02, 2026, 04:08 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  2. identified Sep 02, 2026, 04:35 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  3. identified Sep 02, 2026, 05:04 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  4. identified Sep 02, 2026, 05:32 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  5. identified Sep 02, 2026, 06:02 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  6. identified Sep 02, 2026, 06:31 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  7. identified Sep 02, 2026, 07:00 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  8. identified Sep 02, 2026, 07:32 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  9. identified Sep 02, 2026, 08:00 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  10. identified Sep 02, 2026, 08:30 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  11. identified Sep 02, 2026, 09:00 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  12. identified Sep 02, 2026, 09:30 PM UTC

    The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor the situation on our end and will share further updates as they become available.

  13. identified Sep 02, 2026, 10:07 PM UTC

    Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub. As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1

  14. identified Sep 03, 2026, 12:45 PM UTC

    Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available. To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime. If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force Git to use HTTP/1.1: git config --global http.version HTTP/1.1

  15. resolved Sep 03, 2026, 04:41 PM UTC

    Semaphore is currently operating normally, which is why we’re marking this incident as resolved. GitHub confirmed that the behavior affecting unauthenticated Git operations is the result of an intentional change on their end rather than a bug. You can read their latest statement here: https://github.com/orgs/community/discussions/206581#discussioncomment-18269083 For builds affected by this behavior, the previously shared workaround remains available. Configure Git to use HTTP/1.1 before running the affected Git operation: git config --global http.version HTTP/1.1 We will add this instruction and further context to our documentation. Any additional guidance from Semaphore will be shared through in-app notifications. For further assistance, contact our support team at [email protected].

Read the full incident report →

Minor September 2, 2026 Periodic authentication failure with GitHub repositories 3h 59m Semaphore

Started Sep 02, 2026, 11:17 AM UTC· resolved Sep 02, 2026, 03:16 PM UTC

  1. investigating Sep 02, 2026, 11:17 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 02, 2026, 11:44 AM UTC

    We are still looking into the cause of this issue, but as a temporary workaround, you can add the following environment variable to your jobs, which will cause them to immediately fail and not hang: GIT_TERMINAL_PROMPT=0 After they fail, you can rerun the pipeline, and only the failed jobs should rerun, allowing you to work through this issue until we have more information to share.

  3. investigating Sep 02, 2026, 12:18 PM UTC

    We are continuing to investigate this issue.

  4. identified Sep 02, 2026, 12:53 PM UTC

    We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 Please also note that we are continuing to monitor and investigate this situation on our end.

  5. identified Sep 02, 2026, 01:29 PM UTC

    We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor and investigate this situation on our end.

  6. identified Sep 02, 2026, 01:56 PM UTC

    We have found that this is currently a wider situation impacting HTTPS operations, which is also affecting Semaphore and our users. You can read more about this in this thread: https://github.com/orgs/community/discussions/206581 As a workaround, you can configure git to use only HTTP/1.1, using the following command: git config --global http.version HTTP/1.1 We are continuing to monitor and investigate this situation on our end.

  7. monitoring Sep 02, 2026, 02:19 PM UTC

    There was a wider situation impacting HTTPS operations, which also affected Semaphore and our users https://github.com/orgs/community/discussions/206581 The issue has since appeared to subside, but we're continuing to monitor the situation on our end.

  8. resolved Sep 02, 2026, 03:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 31, 2026 Delays in job processing 10h 4m Semaphore

Started Aug 31, 2026, 12:06 PM UTC· resolved Aug 31, 2026, 10:11 PM UTC

  1. investigating Aug 31, 2026, 12:06 PM UTC

    We are currently investigating this issue.

  2. identified Aug 31, 2026, 12:56 PM UTC

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

  3. identified Aug 31, 2026, 02:10 PM UTC

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

  4. identified Aug 31, 2026, 03:32 PM UTC

    We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.

  5. identified Aug 31, 2026, 04:01 PM UTC

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  6. identified Aug 31, 2026, 04:34 PM UTC

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  7. identified Aug 31, 2026, 05:17 PM UTC

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  8. identified Aug 31, 2026, 05:48 PM UTC

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  9. identified Aug 31, 2026, 05:50 PM UTC

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

  10. identified Aug 31, 2026, 05:58 PM UTC

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

  11. identified Aug 31, 2026, 06:22 PM UTC

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  12. identified Aug 31, 2026, 06:48 PM UTC

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

  13. identified Aug 31, 2026, 07:21 PM UTC

    Our team is continuing to work on a fix for this issue.

  14. identified Aug 31, 2026, 07:49 PM UTC

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

  15. identified Aug 31, 2026, 08:18 PM UTC

    Our engineering team is actively working to resolve this issue.

  16. monitoring Aug 31, 2026, 08:35 PM UTC

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

  17. monitoring Aug 31, 2026, 09:09 PM UTC

    We are continuing to monitor for any further issues.

  18. monitoring Aug 31, 2026, 09:44 PM UTC

    Our team is still monitoring the results.

  19. resolved Aug 31, 2026, 10:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2026 Delays in job processing 1h 52m Semaphore

Started Aug 28, 2026, 07:17 PM UTC· resolved Aug 28, 2026, 09:09 PM UTC

  1. investigating Aug 28, 2026, 07:17 PM UTC

    We are currently investigating this issue.

  2. identified Aug 28, 2026, 08:11 PM UTC

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

  3. monitoring Aug 28, 2026, 08:31 PM UTC

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

  4. resolved Aug 28, 2026, 09:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 27, 2026 Delays in Job Processing 52m Semaphore

Started Aug 27, 2026, 08:09 PM UTC· resolved Aug 27, 2026, 09:01 PM UTC

  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 47m Semaphore

Started Aug 27, 2026, 06:43 PM UTC· resolved Aug 27, 2026, 07:30 PM UTC

  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 6h 11m Semaphore

Started Aug 25, 2026, 08:35 AM UTC· resolved Aug 25, 2026, 02:47 PM UTC

  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 1h 33m Semaphore

Started Aug 21, 2026, 07:14 PM UTC· resolved Aug 21, 2026, 08:47 PM UTC

  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 2h 40m Semaphore

Started Aug 18, 2026, 03:07 PM UTC· resolved Aug 18, 2026, 05:47 PM UTC

  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 1h 25m Semaphore

Started Aug 04, 2026, 10:38 AM UTC· resolved Aug 04, 2026, 12:04 PM UTC

  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 →

Minor July 23, 2026 Delays in job processing 1h 43m Semaphore

Started Jul 23, 2026, 12:35 AM UTC· resolved Jul 23, 2026, 02:18 AM UTC

  1. investigating Jul 23, 2026, 12:35 AM UTC

    We are currently investigating this issue.

  2. investigating Jul 23, 2026, 01:03 AM UTC

    We are continuing to investigate this issue.

  3. identified Jul 23, 2026, 01:25 AM UTC

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

  4. monitoring Jul 23, 2026, 02:00 AM UTC

    A fix has been implemented and we have observed an improvement in job processing. We are continuing to monitor the situation.

  5. resolved Jul 23, 2026, 02:18 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 21, 2026 Some jobs may have issues authenticating with GitHub 5h 10m Semaphore

Started Jul 21, 2026, 08:36 AM UTC· resolved Jul 21, 2026, 01:46 PM UTC

  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 2h 53m Semaphore

Started Jul 17, 2026, 10:32 AM UTC· resolved Jul 17, 2026, 01:25 PM UTC

  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 →