Rewindex

CompaniesSemaphoreIncidents

Semaphore: Some jobs may have issues authenticating with GitHub

MajorStatus: resolvedStarted Resolved (5.2 h)7 updatesstspg.io (opens in new tab)
Part of an outage event

GitHub outage, Jul 21, 2026 · 15 vendors, 19 incidents

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…”

Swipe sideways to see the whole diagram.

blamed AnthropicGitHubposted 10:31 UTCPosted before GitHub did1 vendor, 1 blamed GitHubSemaphoreWithin an hour2 vendors, 2 blamed GitHubHashiCorp, Terraform Cloud (HCP)Later1 vendor, 1 blamed GitHubMintlifyAnthropicposted −20 min, did not name GitHubBolt.new, Cursor−16 min to +7 h 14 minSemaphore (this incident)posted −1 h 54 min
blamed AnthropicGitHubposted 10:31 UTCPosted before GitHub did1 vendor, 1 blamed GitHubSemaphoreWithin an hour2 vendors, 2 blamed GitHubHashiCorp, Terraform Cloud(HCP)Later1 vendor, 1 blamed GitHubMintlifyAnthropicposted −20 min, did not nameGitHubBolt.new, Cursor−16 min to +7 h 14 minSemaphore (this incident)posted −1 h 54 min
Semaphore is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
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

Full event: timeline, evidence and all vendors →

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.

Affected components: Semaphore

Timeline of updates

  1. investigating

    We are currently investigating this issue.

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

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

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

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

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

  7. resolved

    GitHub confirmed that the incident on their end has been resolved. You can review the GitHub update here: https://www.githubstatus.com/incidents/g40zcbvchny4

Changes Rewindex caught on this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Semaphore profileRecent Semaphore incidentsMarkdownJSON