New Multi-region uptime checks and custom-domain status pages

Semaphore CI Outage History

Daily provider-status observations and published incident history for Semaphore CI.

Operational

Semaphore CI is operational. Verified . Official provider source.

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

Aug 18Nov 15

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 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Delays in Job Processing
minor Observed active window 1h 23m

View incident details and source

Started:

Semaphore
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 continuing to investigate this issue.
investigating
We are currently investigating this issue.
Delays in Job Processing
minor Observed active window 3h 15m

View incident details and source

Started:

Semaphore
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
monitoring
We are continuing to monitoring the situation.
monitoring
Job processing times have returned to normal. We're continuing to monitor the situation closely to ensure service continues running as expected.
monitoring
We are starting to see improvements in job processing times, and jobs should be returning to normal.
monitoring
We're continuing to monitor the situation closely and will provide further updates.
identified
The issue has been identified, and we are continuing to monitor the situation.
investigating
We are currently investigating this issue.
Delays in Job Processing
minor Observed active window 2h 43m

View incident details and source

Started:

Semaphore
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.
Delays in Job Processing
minor Observed active window 2h 16m

View incident details and source

Started:

Semaphore
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 continuing to investigate this issue.
investigating
We are currently investigating this issue.
Delays in Job Processing
minor Observed active window 3h 50m

View incident details and source

Started:

Semaphore
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.
monitoring
We are continuing to monitor for any further issues.
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.
Delays in job processing
minor Observed active window 2h 10m

View incident details and source

Started:

Semaphore
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
Jobs are currently experiencing delays during initialization. We are investigating the issue and will share updates as we have more information.
Delays in job processing
minor Observed active window 3h 8m

View incident details and source

Started:

Semaphore
monitoring
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.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
Intermittent network connectivity issues
minor Observed active window 8h 36m

View incident details and source

Started:

Semaphore
monitoring
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.
identified
The issue has been identified.
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.
September 2026
Delays in job processing
major Observed active window 52m

View incident details and source

Started:

Semaphore
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.
Intermittent cache connection errors
minor Observed active window 41m

View incident details and source

Started:

Semaphore
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.

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.

May 2026
Delays when checking out GitHub repos via SSH
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented, and everything should be back to normal. The previously shared snippets can be removed.
identified
We identified slow GitHub operations related to problems with the network, and we deployed a fix to re-route those operations to a healthier server. Some HTTPS operations started to fail because of that. To disable the fix, you should use the command: sudo sed -i 's/^\([0-9].*github\.com\)/#\1/' /etc/hosts And to re-enable, you can use: sudo sed -i 's/^#\([0-9].*github\.com\)/\1/' /etc/hosts
monitoring
A fix has been implemented and we are monitoring the results.
identified
We identified slow communication between Semaphore jobs and GitHub. We are continuing to work with our upstream provider to resolve this. For impacted jobs, please replace the normal checkout command with the following: retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout'" And afterwards, use cd to change the directory to the cloned repository (replace with your project).
Delays when checking out GitHub repos via SSH
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are not currently seeing timeouts related to slow connections. Our team is continuing to monitor the situation to confirm that service has fully returned to normal.
identified
We identified that the issue is slow communication between our jobs and GitHub. We are currently working with our upstream provider to to resolve this. For impacted jobs, please replace the normal checkout command with the following: retry --times 5 "timeout 40 bash -lc 'source ~/.toolbox/toolbox; checkout'" And afterwards, use cd <dir> to change the directory to the cloned repository (replace <dir> with your project).
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue.