Semaphore’s incident blames GitHub as the cause. (hop 1, posted −1 h 54 min vs GitHub’s own post)
“…Some jobs may have issues authenticating with GitHub GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g4…”
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
What changed
Struck in red is what Semaphore removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: Some jobs may have issues authenticating with GitHub
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-07-21 08:36 UTC
AddedResolved time#5
Before: not present
After: 2026-07-21 13:46 UTC
AddedAffected components#6
Before: not present
After: Semaphore
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdateinvestigating#8
Before: not present
After: 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
AddedUpdateinvestigating#9
Before: not present
After: 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
AddedUpdatemonitoring#10
Before: not present
After: 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
AddedUpdatemonitoring#11
Before: not present
After: 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
AddedUpdatemonitoring#12
Before: not present
After: 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
AddedUpdateresolved#13
Before: not present
After: GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here:
https://www.githubstatus.com/incidents/g40zcbvchny4