Semaphore outage, 2 September 2026

Periodic authentication failure with GitHub repositories

Started
Resolved
3 Sept 2026, 16:41 UTC (after 24 h 32 min)
Impact
Minor
Affected
Semaphore

Last update from Semaphore

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

3 Sept 2026, 16:41 UTC

Read the full incident on the official Semaphore status page

Is Semaphore down now?

This page is the record of one past incident. For the live status, see Is Semaphore down right now? - it reads the official status page every 2 minutes.

Other Semaphore incidents

  1. Delays in job processing

  2. Delays in job processing

  3. Intermittent network connectivity issues

  4. Delays in job processing

  5. Intermittent cache connection errors

  6. Delays in job processing

  7. Periodic authentication failure with GitHub repositories

  8. Delays in job processing

All recorded Semaphore incidents