HashiCorp Vault reported this major-impact incident on its official status page on Jul 29, 2026, 12:36 UTC. It was resolved after 8h 8m.
Right now HashiCorp Vault is operational. Live HashiCorp Vault status →
Our Engineering team has pulled v6.57.0 of the AWS provider from the registry and published a fixed v6.57.1.
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.
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.
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.
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.
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