Periodic authentication failure with GitHub repositories
View the provider incident record →Current answer
Semaphore CI experienced a minor incident: Periodic authentication failure with GitHub repositories. ServiceAlert observed recovery on Sep 2, 2026.
Looking for an update now? Check the current status, or follow Semaphore CI for future changes.
Incident Lifecycle
Affected Components
Semaphore
Incident Timeline
Monitoring
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.
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.
Sep 2, 2026 at 2:19 PM UTC
Identified
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.
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.
Sep 2, 2026 at 1:56 PM UTC
Identified
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.
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.
Sep 2, 2026 at 1:29 PM UTC
Identified
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.
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.
Sep 2, 2026 at 12:53 PM UTC
Investigating
We are continuing to investigate this issue.
Sep 2, 2026 at 12:18 PM UTC
Investigating
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.
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.
Sep 2, 2026 at 11:44 AM UTC
Investigating
We are currently investigating this issue.
Sep 2, 2026 at 11:17 AM UTC
Was your business affected by this Semaphore CI outage?
Follow Semaphore CI and route available status alerts to email or a team channel.