rewindex

CompaniesHashiCorpIncidents

HashiCorp: GitHub and Other VCS workloads experiencing intermittent issues

MajorStatus: resolvededitedStarted Resolved (28 h)10 updatesstatus.hashicorp.com (opens in new tab)
Summary

HashiCorp reported a major degradation starting 2026-10-22 17:15 UTC: intermittent GitHub API access issues could cause VCS-based Terraform workloads to malfunction. The incident was still open when archived, open for 0 min at the last update; HashiCorp was monitoring GitHub and awaiting further information.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: HCP Terraform

Timeline of updates

  1. identified

    GitHub.com "GitHub.com": http://GitHub.com (opens in new tab) has acknowledged an issue causing intermittent issues accessing their API. This may cause VCS-based Terraform workloads to malfunction. We are monitoring GitHub status and will update this issue as we learn more.

    Current impact state: VCS workloads experiencing intermittent issues.

    Action underway: Awaiting word from GitHub.com "GitHub.com": http://GitHub.com (opens in new tab)

    Next update time: 17:30 UTC

  2. investigatingEdited

    We are continuing to receive reports of intermittent issues with VCS workloads, some of which are not hosted on GitHub.com "GitHub.com": http://GitHub.com (opens in new tab). Our engineering team is investigating these issues.

    Current impact state: VCS workloads experiencing intermittent issues.

    Action underway: Awaiting word from GitHub.com "GitHub.com": http://GitHub.com (opens in new tab)

    Next update time: 18:00 UTC

  3. investigating

    Our engineering is continuing to investigate intermittent VCS-related failures.

    Current impact state: VCS related workloads experiencing intermittent issues.

    Action underway: Engineering team investigating.

    Next update time: 18:30 UTC

  4. monitoring

    Our engineers are no longer able to reproduce the issue and error counts have dropped off. We will continue to monitor for any further issues. If you experience any further problems please reach out to support.

    Current impact state: System in recovery.

    Action underway: Monitoring.

    Next update time: 19:00 UTC

  5. investigating

    Intermittent and some persistent VCS issues have been reproduced on some workspaces. Our engineering team is continuing to investigate.

    Current impact state: Intermittent issues on VCS workspaces are continuing to be observed.

    Action underway: Engineering team is working on reliably reproducing the issue.

    Next update time: 19:00 UTC

  6. identified

    Our engineering team has identified the tfc-agent release v1.33.2 as the cause of intermittent issues with VCS providers. We have downgraded the version to 1.33.1 for remote runs. If you are experiencing issues with self-hosted agents please downgrade to 1.33.1 until a new release is made to address the issue.

    Current impact state: Remote runs fully-functional. Affected self-hosted agents need to downgrade to tfc-agent version 1.33.1. Stacks users may experience a regression when using proxies with version 1.33.1.

    Action underway: Releasing a fixed tfc-agent version.

    Next update time: 19:45 UTC

  7. monitoring

    Downgrading tfc-agent to 1.33.1 has proven effective in eliminating the intermittent VCS failures. We will continue to monitor for any further impacts. A new release with a fix is in-progress and expected within 24 hours. If you are not affected, do not downgrade. If you experience further issues please contact support.

  8. resolved

    VCS connection issues should be mitigated by downgrading to tfc-agent 1.33.2. Our engineering team is still investigating the cause of this failure. If you do not have any VCS connection problems you do not need to downgrade to 1.33.1. We will release a new version of tfc-agent in the next 24 hours to fix the root cause.

  9. resolved

    One minor correction, VCS connection issues can be mitigated by downgrading tfc-agent from 1.33.2 to 1.33.1.

  10. resolved

    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.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

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

Cite this

Status incident (vendor impact label: major) posted by HashiCorp, started 2026-10-22 17:15 UTC, resolved after 28 h, 10 update(s); edited after publishing.

Title
GitHub and Other VCS workloads experiencing intermittent issues
Vendor
HashiCorp
Date
URL
https://rewindex.com/company/hashicorp/incidents/01M5J9S4598B4CW5PZN0P739CD

HashiCorp profileRecent HashiCorp incidentsAll outages on October 22, 2026HashiCorp in October 2026MarkdownJSON