Semaphore CI Incident History

1. resolvedSep 3 · 16:41 UTC

   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.

Reported by Semaphore CI on their status page.

1. ResolvedSep 3 · 16:41 UTC

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

Reported by Semaphore CI on their status page.

1. resolvedSep 2 · 15:16 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 31 · 22:11 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 28 · 21:09 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 27 · 21:01 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 27 · 19:30 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. ResolvedAug 27 · 19:30 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 25 · 14:47 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. ResolvedAug 25 · 14:47 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 21 · 20:47 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.

1. resolvedAug 18 · 17:47 UTC

   This incident has been resolved.

Reported by Semaphore CI on their status page.