Companies/Semaphore/Incidents

Semaphore: Periodic authentication failure with GitHub repositories

Affected components: Semaphore

Timeline of updates

1. investigating2026-09-02 11:17 UTC

   We are currently investigating this issue.

2. investigating2026-09-02 11:44 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. investigating2026-09-02 12:18 UTC

   We are continuing to investigate this issue.

4. identified2026-09-02 12:53 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. identified2026-09-02 13:29 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. identified2026-09-02 13:56 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. monitoring2026-09-02 14:19 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. resolved2026-09-02 15:16 UTC

   This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Semaphore profileRecent Semaphore incidentsMarkdownJSON