HashiCorp
Apps and SaaS. Source: HashiCorp status page.
- Incidents, last 90 days
- 18
- Median to mitigation
- 1h 27m
- Median to resolution
- 2h 30m
- p95 to resolution
- 5d 6h
- Naming an upstream provider
- 22%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| The text does not say enough to tell | 11 |
| A code release introduced the failure | 2 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 1 |
| Login, tokens, certificates or credentials failed | 1 |
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 1 |
| A provider or third-party service this vendor depends on failed | 1 |
| Network, DNS, routing or connectivity failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Terraform Runs Failing
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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...
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
HCP Vault Azure: Cluster Updates and Creation
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
Names an upstream provider: Azure.
-
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.
-
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.
-
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.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Users unable to access releases.hashicorp.con
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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.
-
investigating
Status: **Investigating** > Users are currently unable to access [releases.hashicorp.com](http://releases.hashicorp.com "releases.hashicorp.com"), resulting in 504 errors. The problem affects terraform provider downloads, and Vault Radar access. Our team is working to identify...
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
HCP Terraform Returning 404s
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are aware of and investigating reports of degraded performance with HCP Terraform. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
investigating
We are continuing to investigate issues with HCP Terraform. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Degraded commit/content scans in HCP Vault Radar
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are aware of and investigating reports of degraded performance handling some commit/content scans. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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.
-
monitoring
Our Engineering team has implemented a fix to resolve the issue. There may still be some higher than normal delays as the backlog is processed. We are monitoring the situation closely and will post an update as soon as the issue is fully resolved.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Hashicorp Linux packages GPG key rotation
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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...
-
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
-
identified
Our engineers have identified the issue and are working through remaining packages.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Errors creating new VCS workspaces with Bitbucket cloud provider
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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.
-
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.
-
monitoring
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.
-
resolved
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Delayed HCP Terraform Runs
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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.
-
monitoring
We've mitigated the delayed HCP Terraform run start times. Customer jobs running on HashiCorp-hosted agents should start without unusual delay.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
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...
-
resolved
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Issues When Downloading Terraform Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
Started during GitHub: Disruption with Login and Release Asset downloads.
-
investigating
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.
-
identified
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...
-
monitoring
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...
-
resolved
3rd party provider downloads are confirmed to be functioning. Please retry any failed Terraform runs, and contact support if you have any further problems.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
DR Cluster Creation Failures
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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...
-
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.
-
resolved
We have implemented a mitigation for the issue affecting new Disaster Recovery (DR) cluster creation. Initial validation has been successful, and new DR cluster creation is functioning as expected. We are continuing to monitor the service to ensure stability before considering...
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Infragraph Snapshot are stuck
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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, and at least two workspaces are affected. Our team is working to identify and resolve the issue. We will post updates...
-
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.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Infragraph Service and UI down
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
HCP Terraform UI Not Loading
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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...
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
app.terraform.io is not loading
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Engineering team is investigating degraded performance and inability to load [app.terraform.io](http://app.terraform.io "app.terraform.io"). We will post updates with more information as it becomes available.
-
monitoring
Our Engineering team has implemented a fix to resolve the issue. [app.terraform.io](http://app.terraform.io "app.terraform.io") should now load. We are continuing to monitor the situation closely and will post an update as soon as the issue is fully resolved.
-
resolved
Our Engineering team has resolved the issue with [app.terraform.io](http://app.terraform.io "app.terraform.io") loading correctly. It should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: AWS.
-
investigating
We are aware of and investigating reports of degraded performance after AWS provider update. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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...
-
monitoring
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry, and continue to work to publish v6.57.1. We will continue to monitor for failures.
-
resolved
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Increased Load Times for HCP Portal
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are aware of and investigating reports of degraded performance. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Terraform Runs Failing to Fetch GitHub Sources Over SSH
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: GitHub.
-
investigating
We are investigating failures cloning GitHub-hosted Terraform modules and sources over SSH, caused by an ongoing upstream GitHub incident affecting SSH deploy keys. Runs using `git::ssh://` or `git@github.com:` sources may fail with Permission denied (publickey); HTTPS and...
-
monitoring
GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue...
-
monitoring
GitHub has completed remediation of the incident affecting SSH deploy keys. Terraform runs using GitHub-hosted modules and sources over SSH have recovered, and clone operations are functioning normally. We are no longer observing related authentication failures and will continue...
-
resolved
GitHub has completed remediation of the SSH deploy key incident. Terraform runs using GitHub-hosted modules/sources over SSH have recovered, clone operations are functioning normally, and no further authentication failures are being observed.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Intermittent Bitbucket Data Center VCS Triggered Terraform run Failures
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are continuing to investigate reports of intermittent issues with VCS-triggered Terraform runs for only workspaces connected to Bitbucket Data Center. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
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.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Terraform releases page experiencing errors
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We continue to investigate new reports of 50x errors when attempting to access [releases.hashicorp.com/terraform/](http://releases.hashicorp.com/terraform/ "releases.hashicorp.com/terraform/"). Our team is working to identify and resolve the issue. We will post updates with more...
-
monitoring
Our Engineering team has implemented a fix to resolve the issue with hitting endpoints on [releases.hashicorp.com/terraform/](http://releases.hashicorp.com/terraform/ "releases.hashicorp.com/terraform/"). We are monitoring the situation closely and will post an update as soon as...
-
resolved
Our Engineering team has resolved the issue. The release page should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Cluster Provisioning and Management Operations Impacted
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating an issue affecting HVD cluster management operations. Customers may experience failures when creating, deleting, or resizing (upscaling) HVD clusters. Existing clusters and Vault operations remain unaffected. Our engineering team is actively...
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Intermittent 5XX errors for registry
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Terraform Registry is experiencing elevated error rates affecting terraform init workflows and documentation access. Our engineering team is investigating the issue.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Cluster Creation Is Failing
Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are aware of the issue that the cluster. creation is failing. We are actively investigating the issue. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available.
-
identified
Our Engineering team has identified the cause to be a a CI build-number drift between app-image and terraform-image jobs in the same workflow run caused the service to reference a non-existent terraform image tag. We are actively working on a fix. Once we have additional...
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.
Terraform Provider Azure RM
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: Azure.
-
investigating
We’re investigating an issue affecting Terraform state refresh for Azure App Service Environment v3 resources. Our Engineering teams are actively investigating the issue. We will update as soon as more information becomes available.
-
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.
-
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.
-
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.
Excerpts are shortened. Read the full incident on HashiCorp's status page.