Looking for an update now? Check the current status, or follow Semaphore CI for future changes.
68.8%of 80 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
October 2026
63.3%
30
11
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)
Aug 17Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we are monitoring the results.
identified
We're starting to see improvements in job processing times, although some delays may still occur. We're continuing to monitor the situation closely and will provide further updates as we make progress.
Network connectivity is returning to normal, and the affected services should no longer be impacted. We will continue monitoring the situation closely.
If you continue to experience similar issues, please contact our support team at support@semaphore.io.
identified
Our investigation has identified intermittent connectivity issues between our infrastructure provider’s network and certain Google services. This may affect artifact uploads and downloads, as well as jobs that depend on Google-hosted resources.
We’ve gathered diagnostic information and are escalating the issue to our infrastructure provider for further investigation.
We’ll continue monitoring the situation and share updates as significant new information becomes available.
investigating
We are continuing to investigate this issue.
investigating
We identified that the intermittent network connectivity issues are likely related to our infrastructure provider's recent maintenance. Although the maintenance is complete, we're still experiencing intermittent connection interruptions and slow network performance.
identified
We are continuing to work on a fix for this issue.
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.
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.
