outages.live
Live
HashiCorpIncident · 2026-08-13 17:50 UTC

Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources

ResolvedOfficial update

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.

The latest update from HashiCorp.

State

Resolved

Started

80 d ago

2026-08-13 17:50 UTC

Lasted

1 h 16 min

until 2026-08-13 19:06 UTC

Worst impact

Degraded

Timeline

2 updates
17:5018:0918:2818:4719:06
DegradedUpdate postedTimes in UTC

Identified

1 h 16 min 100%

Updates

Times in UTC

As posted by HashiCorp

Resolved2026-08-13 19:06 UTC

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.

Identified2026-08-13 17:50 UTC

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" } } } ```

HashiCorp in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

16

Days with an incident

21

Median duration

2 h 29 min

This incident

49% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days
median 2 h 29 min
90 days agoToday

Other HashiCorp incidents

All incidents

HashiCorp·GitHub and Other VCS workloads experiencing intermittent issues

Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.

Resolvedresolved 10 d ago

HashiCorp·Terraform Runs Failing

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.

Resolvedresolved 19 d ago

HashiCorp·HCP Vault Azure: Cluster Updates and Creation

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.

Resolvedresolved 23 d ago

HashiCorp·Users unable to access releases.hashicorp.con

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.

Resolvedresolved 36 d ago

HashiCorp·HCP Terraform Returning 404s

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.

Resolvedresolved 39 d ago

Follow HashiCorp

Your coding agent knows when HashiCorp is down, and tells you when a failure is theirs, not yours. You can also get HashiCorp incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hashicorp" and tell me if HashiCorp has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=hashicorp
Slack
/feed subscribe https://outages.cc/feed.xml?providers=hashicorp

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane