Is HashiCorp down?

Status: Identified GitHub.com "GitHub.com": http://GitHub.com 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 Next update time: 17:30 UTC Affected components HCP Terraform (Partial outage)

Status: Investigating 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. 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 Next update time: 18:00 UTC Affected components HCP Terraform (Partial outage)

Status: 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 Affected components HCP Terraform (Partial outage)

Status: 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 Affected components HCP Terraform (Partial outage)

Status: 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 Affected components HCP Terraform (Partial outage)

Status: 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 Affected components HCP Terraform (Partial outage)

Status: 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. Affected components HCP Terraform (Partial outage)

Status: 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. Affected components HCP Terraform (Operational)

Status: Resolved One minor correction, VCS connection issues can be mitigated by downgrading tfc-agent from 1.33.2 to 1.33.1. Affected components HCP Terraform (Operational)

Status: 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. Affected components HCP Terraform (Operational)

Status: Investigating HCP Terraform and HCP Waypoint will undergo scheduled maintenance on Saturday November 14th 2026, beginning at 17:00 UTC. This maintenance is necessary to improve performance and increase capacity. We expect this maintenance to complete in under 5 hours. These services will be unavailable until maintenance completes. Customers will not be able to manually or automatically trigger Terraform operations during maintenance. Updates will be posted as necessary throughout the maintenance period. The next update will be posted before October 20th.

Status: Investigating Some customers are seeing terraform applies fail. The pre‑apply run task receives an “Unexpected response from broker: Status code: 424, Message: Failed Dependency” error. Our Engineering team is working to identify and resolve the issue. We will post updates with more information as it becomes available. Affected components HCP Terraform (Degraded performance)

Status: Monitoring Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Affected components HCP Terraform (Partial outage)

Status: Resolved Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Affected components HCP Terraform (Operational)

Status: Investigating We are aware of an issue affecting cluster updates and cluster creation on HCP Vault Dedicated Azure clusters. Our team is actively investigating. We will provide updates as more information becomes available.

Status: Monitoring Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.

Status: Monitoring Our fixes reduced the damage, but it did not fully resolve the issue. The team is actively investigating. We will provide updates as more information becomes available.

Status: Monitoring We have identified the root cause and fixed the issue. All operations should work seamlessly. We will keep monitoring and will provide updates as more information becomes available.

Status: Resolved Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

Status: Investigating Users are currently unable to access releases.hashicorp.com, resulting in 504 errors. The problem affect terraform provider downloads, and Vault Radar access. HashiCorp is investigating the problem and will provide further status update updates.

Status: Investigating Status: Investigating "Users are currently unable to access releases.hashicorp.com "releases.hashicorp.com": http://releases.hashicorp.com, resulting in 504 errors. The problem affects terraform provider downloads, and Vault Radar access. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available. "

Status: Monitoring Our Engineering team has implemented a fix to resolve the issue. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved. Affected components Releases Site (Partial outage)

Status: Resolved Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team. Affected components Releases Site (Operational)