HashiCorp outage, 22 October 2026

GitHub and Other VCS workloads experiencing intermittent issues

Started
Resolved
22 Oct 2026, 20:01 UTC (after 2 h 45 min)
Impact
Major

Is this still happening?

No. HashiCorp marked this incident resolved on 22 Oct 2026, 20:01 UTC, 2 h 45 min after it began.

Right now: HashiCorp reports all systems operational. (as of 26 Oct, 03:45 UTC) Live HashiCorp status

Last update from HashiCorp

Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.

23 Oct 2026, 21:07 UTC

Other HashiCorp incidents

  1. HCP Terraform Scheduled Maintenance (2026-11-14)

  2. Terraform Runs Failing

  3. HCP Vault Azure: Cluster Updates and Creation

  4. Users unable to access releases.hashicorp.con

  5. HCP Terraform Returning 404s

  6. Degraded commit/content scans in HCP Vault Radar

  7. Hashicorp Linux packages GPG key rotation

  8. Errors creating new VCS workspaces with Bitbucket cloud provider

All recorded HashiCorp incidents