Sep <var data-var='date'>17</var>, <var data-var='time'>15:09</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>17</var>, <var data-var='time'>14:47</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>17</var>, <var data-var='time'>14:29</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>17</var>, <var data-var='time'>14:17</var> UTC Investigating - We are currently investigating this issue.

Delays in job processing

Sep <var data-var='date'>17</var>, <var data-var='time'>14:12</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>17</var>, <var data-var='time'>13:56</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>17</var>, <var data-var='time'>13:52</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>17</var>, <var data-var='time'>13:33</var> UTC Investigating - We are currently investigating this issue.

Intermittent cache connection errors

Sep <var data-var='date'>15</var>, <var data-var='time'>16:46</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'>15</var>, <var data-var='time'>16:16</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>15</var>, <var data-var='time'>15:49</var> UTC Update - We are continuing to work on a fix for this issue. Sep <var data-var='date'>15</var>, <var data-var='time'>14:52</var> UTC Identified - The issue has been identified and a fix is being implemented. Sep <var data-var='date'>15</var>, <var data-var='time'>14:45</var> UTC Investigating - We are currently investigating this issue.

Sep <var data-var='date'> 3</var>, <var data-var='time'>16:41</var> UTC Resolved - 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 support@semaphore.io. Sep <var data-var='date'> 3</var>, <var data-var='time'>12:45</var> UTC Update - 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 Sep <var data-var='date'> 2</var>, <var data-var='time'>22:07</var> UTC Update - 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 Sep <var data-var='date'> 2</var>, <var data-var='time'>21:30</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>21:00</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>20:30</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>20:00</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>19:32</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>19:00</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>18:31</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>18:02</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>17:32</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>17:04</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>16:35</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>16:08</var> UTC Identified - 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.

Periodic authentication failure with GitHub repositories

Sep <var data-var='date'> 2</var>, <var data-var='time'>15:16</var> UTC Resolved - This incident has been resolved. Sep <var data-var='date'> 2</var>, <var data-var='time'>14:19</var> UTC Monitoring - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>13:56</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>13:29</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>12:53</var> UTC Identified - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>12:18</var> UTC Update - We are continuing to investigate this issue. Sep <var data-var='date'> 2</var>, <var data-var='time'>11:44</var> UTC Update - 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. Sep <var data-var='date'> 2</var>, <var data-var='time'>11:17</var> UTC Investigating - We are currently investigating this issue.

Aug <var data-var='date'>31</var>, <var data-var='time'>22:11</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>31</var>, <var data-var='time'>21:44</var> UTC Update - Our team is still monitoring the results. Aug <var data-var='date'>31</var>, <var data-var='time'>21:09</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>31</var>, <var data-var='time'>20:35</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>31</var>, <var data-var='time'>20:18</var> UTC Update - Our engineering team is actively working to resolve this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>19:49</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>19:21</var> UTC Update - Our team is continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>18:48</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>18:22</var> UTC Update - 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. Aug <var data-var='date'>31</var>, <var data-var='time'>17:58</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>17:50</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>17:48</var> UTC Update - 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. Aug <var data-var='date'>31</var>, <var data-var='time'>17:17</var> UTC Update - 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. Aug <var data-var='date'>31</var>, <var data-var='time'>16:34</var> UTC Update - 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. Aug <var data-var='date'>31</var>, <var data-var='time'>16:01</var> UTC Update - 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. Aug <var data-var='date'>31</var>, <var data-var='time'>15:32</var> UTC Update - We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service. Aug <var data-var='date'>31</var>, <var data-var='time'>14:10</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>31</var>, <var data-var='time'>12:56</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>31</var>, <var data-var='time'>12:06</var> UTC Investigating - We are currently investigating this issue.

Aug <var data-var='date'>28</var>, <var data-var='time'>21:09</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>28</var>, <var data-var='time'>20:31</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>28</var>, <var data-var='time'>20:11</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>28</var>, <var data-var='time'>19:17</var> UTC Investigating - We are currently investigating this issue.

Aug <var data-var='date'>27</var>, <var data-var='time'>21:01</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>27</var>, <var data-var='time'>20:35</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>27</var>, <var data-var='time'>20:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>27</var>, <var data-var='time'>20:11</var> UTC Update - We are continuing to investigate this issue. Aug <var data-var='date'>27</var>, <var data-var='time'>20:09</var> UTC Investigating - We are currently investigating this issue.

Delays in Job Processing

Aug <var data-var='date'>27</var>, <var data-var='time'>19:30</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>27</var>, <var data-var='time'>19:15</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>27</var>, <var data-var='time'>19:00</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>27</var>, <var data-var='time'>18:43</var> UTC Identified - The issue has been identified and a fix is being implemented.

Platform Outage

Aug <var data-var='date'>25</var>, <var data-var='time'>14:47</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>25</var>, <var data-var='time'>14:17</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>25</var>, <var data-var='time'>14:00</var> UTC Identified - We have observed continued impact while monitoring. The issue remains identified, and our team is working on a resolution. Aug <var data-var='date'>25</var>, <var data-var='time'>12:57</var> UTC Update - We are continuing to monitor for any further issues. Aug <var data-var='date'>25</var>, <var data-var='time'>09:19</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>25</var>, <var data-var='time'>08:44</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>25</var>, <var data-var='time'>08:35</var> UTC Investigating - We are currently investigating this issue.

Degraded performance on r1-standard machines

Aug <var data-var='date'>22</var>, <var data-var='time'>11:00</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>22</var>, <var data-var='time'>09:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'> 7</var>, <var data-var='time'>13:07</var> UTC Scheduled - The platform may experience degraded performance during the maintenance window, including up to 15 minutes of downtime.

Scheduled Semaphore Maintenance

Aug <var data-var='date'>21</var>, <var data-var='time'>20:47</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>21</var>, <var data-var='time'>20:27</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>21</var>, <var data-var='time'>20:03</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>21</var>, <var data-var='time'>19:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>21</var>, <var data-var='time'>19:14</var> UTC Investigating - We are currently investigating this issue.

Issues with Bitbucket integration

Aug <var data-var='date'>18</var>, <var data-var='time'>17:47</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'>18</var>, <var data-var='time'>17:16</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>18</var>, <var data-var='time'>16:28</var> UTC Update - We are continuing to work on a fix for this issue. Aug <var data-var='date'>18</var>, <var data-var='time'>15:28</var> UTC Identified - The issue is still ongoing, and the engineering team is actively working on a fix. Aug <var data-var='date'>18</var>, <var data-var='time'>15:24</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'>18</var>, <var data-var='time'>15:18</var> UTC Identified - The issue has been identified and a fix is being implemented. Aug <var data-var='date'>18</var>, <var data-var='time'>15:15</var> UTC Update - Jobs configured to run on F1 machines may take longer than usual to start. Aug <var data-var='date'>18</var>, <var data-var='time'>15:07</var> UTC Investigating - We are currently investigating this issue.

Delays in job processing - F1 machines

Aug <var data-var='date'> 4</var>, <var data-var='time'>12:04</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'> 4</var>, <var data-var='time'>11:30</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Aug <var data-var='date'> 4</var>, <var data-var='time'>10:38</var> UTC Identified - The issue has been identified and a fix is being implemented.

Bitbucket integration may currently be experiencing issues

Jul <var data-var='date'>23</var>, <var data-var='time'>02:18</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>23</var>, <var data-var='time'>02:00</var> UTC Monitoring - A fix has been implemented and we have observed an improvement in job processing. We are continuing to monitor the situation. Jul <var data-var='date'>23</var>, <var data-var='time'>01:25</var> UTC Identified - The issue has been identified and a fix is being implemented. Jul <var data-var='date'>23</var>, <var data-var='time'>01:03</var> UTC Update - We are continuing to investigate this issue. Jul <var data-var='date'>23</var>, <var data-var='time'>00:35</var> UTC Investigating - We are currently investigating this issue.

Jul <var data-var='date'>21</var>, <var data-var='time'>13:46</var> UTC Resolved - GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4 Jul <var data-var='date'>21</var>, <var data-var='time'>12:18</var> UTC Update - 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 <var data-var='date'>21</var>, <var data-var='time'>10:53</var> UTC Update - 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 <var data-var='date'>21</var>, <var data-var='time'>09:25</var> UTC 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 <var data-var='date'>21</var>, <var data-var='time'>09:06</var> UTC Update - 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 <var data-var='date'>21</var>, <var data-var='time'>08:49</var> UTC Update - 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 <var data-var='date'>21</var>, <var data-var='time'>08:36</var> UTC Investigating - We are currently investigating this issue.

Some jobs may have issues authenticating with GitHub

Jul <var data-var='date'>17</var>, <var data-var='time'>13:25</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>17</var>, <var data-var='time'>10:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>17</var>, <var data-var='time'>10:32</var> UTC Investigating - We are currently investigating this issue.

Some features may currently be unresponsive

Jul <var data-var='date'>17</var>, <var data-var='time'>01:05</var> UTC Resolved - This incident has been resolved. Jul <var data-var='date'>17</var>, <var data-var='time'>00:43</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jul <var data-var='date'>17</var>, <var data-var='time'>00:21</var> UTC Investigating - We are currently investigating this issue.

Jun <var data-var='date'>24</var>, <var data-var='time'>21:26</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>24</var>, <var data-var='time'>21:16</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>24</var>, <var data-var='time'>21:07</var> UTC Identified - The issue has been identified and a fix is being implemented. Jun <var data-var='date'>24</var>, <var data-var='time'>21:01</var> UTC Investigating - We are currently investigating this issue.

Elevated error rates

Jun <var data-var='date'>10</var>, <var data-var='time'>16:22</var> UTC Resolved - This incident has been resolved. Jun <var data-var='date'>10</var>, <var data-var='time'>16:14</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>10</var>, <var data-var='time'>15:20</var> UTC Update - The issue has been identified, and our team is implementing a fix. Jun <var data-var='date'>10</var>, <var data-var='time'>15:12</var> UTC Identified - We're experiencing an elevated level of 500's errors and are currently looking into the issue.

Elevated Error Rates

May <var data-var='date'>20</var>, <var data-var='time'>15:32</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>20</var>, <var data-var='time'>15:02</var> UTC Monitoring - A fix has been implemented, and everything should be back to normal. The previously shared snippets can be removed. May <var data-var='date'>20</var>, <var data-var='time'>13:59</var> UTC 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 <var data-var='date'>20</var>, <var data-var='time'>12:48</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. May <var data-var='date'>20</var>, <var data-var='time'>08:44</var> UTC 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).

Delays when checking out GitHub repos via SSH

May <var data-var='date'>19</var>, <var data-var='time'>15:42</var> UTC Resolved - This incident has been resolved. May <var data-var='date'>19</var>, <var data-var='time'>15:10</var> UTC 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 <var data-var='date'>19</var>, <var data-var='time'>11:18</var> UTC 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 <var data-var='date'>19</var>, <var data-var='time'>10:38</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'>19</var>, <var data-var='time'>10:00</var> UTC Investigating - We are currently investigating this issue.

Mar <var data-var='date'>12</var>, <var data-var='time'>17:45</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>12</var>, <var data-var='time'>17:11</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>12</var>, <var data-var='time'>17:03</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>12</var>, <var data-var='time'>15:55</var> UTC Investigating - We are currently investigating this issue.

Mar <var data-var='date'>11</var>, <var data-var='time'>17:42</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>11</var>, <var data-var='time'>17:18</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>11</var>, <var data-var='time'>16:28</var> UTC Identified - The issue has been identified and a fix is being implemented.

Mar <var data-var='date'> 8</var>, <var data-var='time'>18:52</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 8</var>, <var data-var='time'>18:22</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'> 8</var>, <var data-var='time'>17:26</var> UTC Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'> 8</var>, <var data-var='time'>16:25</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'> 8</var>, <var data-var='time'>15:21</var> UTC Investigating - We are currently investigating this issue.

Is Semaphore CI down?

Semaphore CI status is UP

Lastest published events

Delays in job processing

Intermittent cache connection errors

Delays in job processing

Semaphore CI Services, Components and Regions

Recent Semaphore CI events

Delays in job processing

Intermittent cache connection errors

Delays in job processing

Periodic authentication failure with GitHub repositories

Periodic authentication failure with GitHub repositories

Delays in job processing