Semaphore incident

Periodic authentication failure with GitHub repositories

Minor Resolved View vendor source →

Semaphore experienced a minor incident on September 2, 2026 affecting Semaphore, lasting 3h 59m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 11:17 AM UTC
Resolved
Sep 02, 2026, 03:16 PM UTC
Duration
3h 59m
Detected by Pingoru
Sep 02, 2026, 11:17 AM UTC

Affected components

Semaphore

Update timeline

  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.