HashiCorp Outage History

Status: Identified Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update. Affected components HCP Terraform (Full outage)

Status: Identified Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update. Affected components HCP Vault Radar (Degraded performance)

Status: Identified Delays on scans should be minimal at this time, but may still be elevated from normal. Our engineering team is continuing to work on a more permanent fix. Affected components HCP Vault Radar (Degraded performance)

Status: Identified 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. Affected components Linux Package Archive Site (Partial outage) APT Repository (Partial outage)

Status: Identified 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 Affected components RPM Repository (Partial outage) Linux Package Archive Site (Partial outage) APT Repository (Partial outage)

Status: Identified Our engineers have identified the issue and are working through remaining packages. Affected components RPM Repository (Partial outage) Linux Package Archive Site (Partial outage) APT Repository (Partial outage)

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

Status: Identified 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" } } } Affected components HCP Terraform (Degraded performance)

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

Status: Identified Many customers are seeing failed Terraform runs with SIC-001 errors or 403 forbidden responses. We have confirmed around 220 similar errors in VCS audit logs. We have found the root cause and are working on a fix. Once we have additional information, we will share another update. Affected components HCP Terraform (Degraded performance)

Status: Identified We have identified an issue affecting the creation of new Disaster Recovery (DR) clusters. Customers attempting to create a DR cluster may encounter provisioning failures. Our engineering team has identified the cause and is working on a resolution. Existing clusters and workloads are not impacted. We will provide updates as more information becomes available.

Status: Identified Customers may see a blank, white screen while using HCP Terraform. This outage currently only impacts the UI; API calls, CI integrations, and CLI usage should not be affected at this time. Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update. Affected components HCP Terraform (Partial outage)

Status: Identified Our Engineering team has identified the cause and we are actively working on a fix. A workaround would be to pin the aws provider to v6.56.0 till the fixed patch is released. Once we have additional information, we will share another update. Affected components HCP Terraform (Partial outage)

Status: Identified Our Engineering team has identified the cause and we are actively working on a fix to publish a patch version of v6.57.1 and pull v6.57.0 from the registry. Prior to that we advise working around the issue by pinning the AWS provider to v6.56.0. Once we have additional information, we will share another update. Affected components HCP Terraform (Partial outage)

Status: Identified Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update.

Status: Identified Terraform Registry is experiencing elevated error rates affecting terraform init workflows and documentation access. Our Engineering team has identified the cause and we are actively working on a fix. Once we have additional information, we will share another update. Affected components Terraform Registry (Degraded performance)

Status: Identified Our engineering team has identified the cause as an upstream platform change, and we’re actively coordinating with the relevant provider while we work toward a fix. We’ll share another update as soon as we have more information. Affected components HCP Terraform (Degraded performance)

Status: Identified Our engineering team continues to coordinate with the relevant provider while we work toward a fix. We’ll share another update as soon as we have more information. Affected components HCP Terraform (Degraded performance)

Status: Identified Our engineers have identified a malfunction preventing HCP Vault Radar scanning jobs from launching. We're working to resume processing new jobs as soon as possible. Scanning jobs will queue up and be processed once the malfunction has cleared. Affected components HCP Vault Radar (Degraded performance)

Status: Identified Our engineering team has un-blocked new Vault Radar scanning jobs. The system is working through a backlog of jobs accumulated during the malfunction. We're working to scale up workers to process the backlog more quickly. Affected components HCP Vault Radar (Degraded performance)

Status: Identified Our Engineering team has identified the cause Our Engineering team has identified the cause to be with an upstream provider. We are working with the provider to restore functionality as soon as possible. Once we have additional information, we will share another update. Affected components HCP Portal (Degraded performance)