Some jobs may have issues authenticating with GitHub
Incident Lifecycle
Incident Timeline
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
We are continuing to monitor the situation. You can review the GitHub update here:
https://www.githubstatus.com/incidents/g40zcbvchny4
Jul 21, 2026 at 12:18 PM UTC
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
https://www.githubstatus.com/incidents/g40zcbvchny4
Jul 21, 2026 at 10:53 AM UTC
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
Jul 21, 2026 at 9:25 AM UTC
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
You can find the instructions on how to do that here: https://docs.semaphore.io/using-semaphore/connect-github#deploy-key
Jul 21, 2026 at 9:06 AM UTC
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
Read more about it here: https://docs.semaphore.io/reference/toolbox#cache-full-clone
Jul 21, 2026 at 8:49 AM UTC
Investigating
We are currently investigating this issue.
Jul 21, 2026 at 8:36 AM UTC
Was your business affected by this Semaphore CI outage?
Follow Semaphore CI and route available status alerts to email or a team channel.