Outage in Semaphore
Periodic authentication failure with GitHub repositories
Resolved MinorIncident Report
Summary AI Generated
Semaphore 2.0 experienced periodic authentication failures with GitHub repositories over approximately 4 hours due to a broader GitHub-side outage affecting HTTPS operations. Users faced disrupted CI/CD pipelines, with jobs hanging or failing during git authentication. The issue was resolved once the underlying GitHub HTTPS problem subsided, with a temporary workaround available to force HTTP/1.1 via git config.
We are currently investigating this issue.
Components affected
Semaphore 2.0Trusted by 1,000+ teams
The Status Page Aggregator with Early Outage Detection
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
1 day ago - at 09/02/2026 03:16PM
This incident has been resolved.
MONITORING
1 day ago - at 09/02/2026 02:19PM
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.
IDENTIFIED
1 day ago - at 09/02/2026 01:56PM
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.
IDENTIFIED
1 day ago - at 09/02/2026 01:29PM
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.
IDENTIFIED
1 day ago - at 09/02/2026 12:53PM
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.
INVESTIGATING
1 day ago - at 09/02/2026 12:18PM
We are continuing to investigate this issue.
INVESTIGATING
1 day ago - at 09/02/2026 11:44AM
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.
INVESTIGATING
1 day ago - at 09/02/2026 11:17AM
We are currently investigating this issue.
Latest Semaphore outages
Delays in job processing - 3 days ago
Delays in job processing - 6 days ago
Delays in Job Processing - 7 days ago
Platform Outage - 7 days ago
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
