Semaphore outage history

We are currently investigating this issue.

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

We are currently investigating this issue.

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

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

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

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

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

This incident has been resolved.

We are continuing to monitor for any further issues.

We are currently investigating this issue.

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

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

This incident has been resolved.

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

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

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.

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

We are continuing to monitor the situation.

This incident has been resolved.

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

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

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.

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

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified.

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

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.

We are continuing to investigate this issue.

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.

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

This incident has been resolved.

We are currently investigating this issue.

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

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

This incident has been resolved.

We are currently investigating this issue.

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

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

This incident has been resolved.

We are currently investigating this issue.

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

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

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

This incident has been resolved.

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.

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

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

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

We are currently investigating this issue.

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.

We are continuing to investigate this issue.

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.

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.

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.

This incident has been resolved.

We are currently investigating this issue.

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

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

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.

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

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

Our engineering team is actively working to resolve this issue.

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

We are continuing to monitor for any further issues.

Our team is still monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

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

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

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

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

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

This incident has been resolved.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently investigating this issue.

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

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

We are continuing to monitor for any further issues.

We have observed continued impact while monitoring. The issue remains identified, and our team is working on a resolution.

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

This incident has been resolved.

We are currently investigating this issue.

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

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

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

This incident has been resolved.

We are currently investigating this issue.

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

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

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

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

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

This incident has been resolved.