Semaphore incident
Some jobs may have issues authenticating with GitHub
Semaphore experienced a major incident on July 21, 2026 affecting Semaphore, lasting 5h 10m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 21, 2026, 08:36 AM UTC
We are currently investigating this issue.
- investigating Jul 21, 2026, 08:49 AM UTC
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 Jul 21, 2026, 09:06 AM UTC
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
- monitoring Jul 21, 2026, 09:25 AM UTC
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
- monitoring Jul 21, 2026, 10:53 AM UTC
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 Jul 21, 2026, 12:18 PM UTC
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
- resolved Jul 21, 2026, 01:46 PM UTC
GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4