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 3, 2026.
Looking for an update now? Check the current status, or follow Semaphore CI for future changes.
Incident Lifecycle
Affected Components
Semaphore
Incident Timeline
Identified
Our engineers are actively monitoring the intermittent issue affecting Git operations over HTTPS. We will share another update when more information becomes available.
To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.
If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force G...
To prevent affected builds from stalling while waiting for credentials, our engineering team has implemented fail-fast behavior. Affected builds will now fail promptly, reducing unnecessary runtime.
If the issue persists after rerunning the job, add the following command to the job before the affected Git operation to force G...
Sep 3, 2026 at 12:45 PM UTC
Identified
Our engineers are actively monitoring the ongoing situation affecting HTTPS operations: https://github.com/orgs/community/discussions/206581. We’ll share the next update once we have new information from GitHub.
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
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
Sep 2, 2026 at 10:07 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 9:30 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 9:00 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 8:30 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 8:00 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 7:32 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 7:00 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 6:31 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 6:02 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 5:32 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 5:04 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 4:35 PM UTC
Identified
The wider situation impacting HTTPS operations, which is also affecting Semaphore and our users, has started occurring again:
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 the situation on our end and will share further updates as they become available.
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 the situation on our end and will share further updates as they become available.
Sep 2, 2026 at 4:08 PM UTC
Was your business affected by this Semaphore CI outage?
Follow Semaphore CI and route available status alerts to email or a team channel.