# Semaphore: Some jobs may have issues authenticating with GitHub

- Impact (vendor’s label): major
- Status: resolved
- Started: 2026-07-21 08:36 UTC · Resolved: 2026-07-21 13:46 UTC · Duration: 5.2 h
- Updates: 7 · Affected components: Semaphore
- [Vendor status page: https://stspg.io/wv1mj0y1hqwv](https://stspg.io/wv1mj0y1hqwv)
- [Company: Semaphore](https://rewindex.com/company/semaphore.md)

## Part of an outage event

- [GitHub outage, Jul 21, 2026: 15 vendors, 19 incidents](https://rewindex.com/events/2026-07-21-github)
- This incident blames GitHub as the cause. (hop 1, posted −1 h 54 min vs GitHub’s own post)
- Evidence: “…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…”

```mermaid
flowchart LR
  root["GitHub<br/>posted 10:31 UTC"]:::root
  before["Posted before GitHub did<br/>1 vendor, 1 blamed GitHub<br/>Semaphore"]:::blames
  root --> before
  h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>HashiCorp, Terraform Cloud (HCP)"]:::blames
  root --> h1
  later["Later<br/>1 vendor, 1 blamed GitHub<br/>Mintlify"]:::blames
  root --> later
  p0["Anthropic<br/>posted −20 min, did not name GitHub"]:::timing
  root -.-> p0
  k0["Bolt.new, Cursor<br/>−16 min to +7 h 14 min"]:::hop2
  p0 -->|"blamed Anthropic"| k0
  me["Semaphore (this incident)<br/>posted −1 h 54 min"]:::me
  before --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **investigating** 2026-07-21 08:36 UTC: We are currently investigating this issue.
- **investigating** 2026-07-21 08:49 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** 2026-07-21 09:06 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** 2026-07-21 09:25 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** 2026-07-21 10:53 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** 2026-07-21 12:18 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** 2026-07-21 13:46 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

## Rewindex changes for this incident

- 2026-07-21 08:36 UTC: [Major incident: Some jobs may have issues authenticating with GitHub](https://rewindex.com/change/iaa7411f45abf68.md)


---
Canonical: https://rewindex.com/company/semaphore/incidents/tglscp6484t1 · Markdown: https://rewindex.com/company/semaphore/incidents/tglscp6484t1.md · JSON: https://rewindex.com/api/v1/companies/semaphore/incidents/tglscp6484t1 · Generated 2026-10-19T23:15:30.351Z