HashiCorp Vault reported this minor-impact incident on its official status page on Aug 13, 2026, 17:50 UTC. It was resolved after 1h 16m.
Right now HashiCorp Vault is operational. Live HashiCorp Vault status →
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" } } } ```
Our 5-minute checks didn't record a change in HashiCorp Vault's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
HashiCorp Vault reported 15 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 2h 19m. See HashiCorp Vault's uptime and incident history