Looking for an update now? Check the current status, or follow Semaphore CI for future changes.
72.2%of 36 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
76.7%
30
7
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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...
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Periodic authentication failure with GitHub repositories
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
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
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
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
We are continuing to investigate this issue.
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.
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
Our engineering team is actively working to resolve this issue.
identified
We are continuing to work on a fix for this issue.
identified
Our team is continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
identified
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
identified
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
identified
We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.
identified
We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
Legacy Incident Archive
12 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Degraded performance on r1-standard machines
minorSource not attested
Last archived state: resolved
View archived record details
Semaphore
identified
We are continuing to work on a fix for this issue.
identified
We have observed continued impact while monitoring. The issue remains identified, and our team is working on a resolution.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Issues with Bitbucket integration
majorSource not attested
Last archived state: resolved
View archived record details
Semaphore
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Delays in job processing - F1 machines
minorSource not attested
Last archived state: resolved
View archived record details
Semaphore
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
The issue is still ongoing, and the engineering team is actively working on a fix.
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
Jobs configured to run on F1 machines may take longer than usual to start.
investigating
We are currently investigating this issue.
Bitbucket integration may currently be experiencing issues
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
July 2026
Delays in job processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we have observed an improvement in job processing. We are continuing to monitor the situation.
identified
The issue has been identified and a fix is being implemented.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Some jobs may have issues authenticating with GitHub
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
GitHub confirmed that the incident on their end has been resolved, and services should now be returning to normal.
We are continuing to monitor the situation. You can review the GitHub update here:
https://www.githubstatus.com/incidents/g40zcbvchny4
monitoring
We are continuing to monitor the situation, and you can follow the current GitHub incident at the following link:
https://www.githubstatus.com/incidents/g40zcbvchny4
monitoring
Our team is monitoring the situation. If you are affected, please regenerate your deploy key by following the instructions on this page: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key
investigating
Our engineering team is still investigating and working on this issue, but as a current workaround, you can regenerate your GitHub deployment key.
You can find the instructions on how to do that here: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key
investigating
As a workaround to get more consistent builds during this time, please try adding the --use-cache flag to your checkout command.
Read more about it here: https://docs.semaphore.io/reference/toolbox#cache-full-clone
investigating
We are currently investigating this issue.
Some features may currently be unresponsive
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
Delays in job processing
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
June 2026
Elevated error rates
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Elevated Error Rates
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified, and our team is implementing a fix.
identified
We're experiencing an elevated level of 500's errors and are currently looking into the issue.
