HashiCorp

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.

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.

Our engineers have identified the issue and are working through remaining packages.

We have updated the keys in the apt and rpm repos and the documentation. Our engineers are working to identify and re-sign packages signed with the older key

We are currently updating documentation and package verification guidance following an ongoing **GPG** key rotation for all HashiCorp Linux packages. The fingerprint currently displayed on our site is outdated and may not match the active signing key. We are actively updating the published fingerprint information and related documentation. We will provide an update once the corrected fingerprint details are available.

Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to experience any problems, please open a ticket with our support team.

Our Engineering team has implemented a fix for errors when creating new VCS workspaces with the Bitbucket cloud provider. We are continuing to monitor the situation and will post an update as soon as the issue is fully resolved.

Our Engineering team has identified the cause of errors when creating new VCS workspaces with the Bitbucket cloud provider. We are actively working on a fix. Once we have additional information, we will share another update.

We are aware of and investigating reports of errors when creating new VCS workspaces using the Bitbucket cloud provider. We are working to identify and resolve the issue and will post updates with more information when it is available.

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.

We've mitigated the delayed HCP Terraform run start times. Customer jobs running on HashiCorp-hosted agents should start without unusual delay.

Our engineering team is investigating elevated Terraform Cloud run start times on HashiCorp-hosted agents, In some cases, runs are taking about 10 minutes to start.

Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

Our engineering team has identified the cause of the "Missing Resource Identity After Read" errors and has completed a fix. We are preparing version 6.60.0 of the Terraform AWS Provider, which includes this fix. v6.60.0 is not yet available in the registry. This affects `aws_network_acl_rule` resources that were created with provider versions earlier than 6.39.0. Terraform runs that do not manage `aws_network_acl_rule `resources are unaffected. Users encountering errors can continue running Terraform by pinning the provider to version 6.58.0: ``` terraform { required_providers { aws = { source = "hashicorp/aws" version = "6.58.0" } } } ```

3rd party provider downloads are confirmed to be functioning. Please retry any failed Terraform runs, and contact support if you have any further problems.

GitHub has [reported resolution of their issues](https://www.githubstatus.com/incidents/lsvy8xsf0gxv "reported resolution of their issues"). 3rd party providers should be downloadable again. Please retry any failed Terraform runs and contact support if you continue to have problems.

3rd-party Terraform providers hosted on GitHub are experiencing download issues. Official providers are unaffected. [GitHub is investigating the problem](https://www.githubstatus.com/incidents/lsvy8xsf0gxv "GitHub is investigating the problem"). We will update this status page when we have more information.

We are aware of and investigating reports of intermittent failures when downloading Terraform providers. Our team is working to identify the issue. We will post updates with more information as it becomes available.