- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 28of 100
What to do
Check whether your product depends on HCP Terraform. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 16m it lasted.
Anything that failed between 2026-08-13 17:50 UTC and 2026-08-13 19:06 UTC may need a replay.Subscribe to HCP Terraform's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=terraform-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from HCP Terraform 2
- 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" } } } ```
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-549e4fc7ab
Is HCP Terraform still down?
No, this incident was resolved 2026-08-13 19:06 UTC. For HCP Terraform's live state, see https://down.guide/terraform-cloud.
How long did it last?
1h 16m, from 2026-08-13 17:50 UTC to 2026-08-13 19:06 UTC, by the times HCP Terraform posted.
What caused it?
HCP Terraform hasn't published a root cause. If it does, it shows here.
Where does this come from?
HCP Terraform's official status page, https://status.hashicorp.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.