New Multi-region uptime checks and custom-domain status pages

HCP Terraform Outage History

Daily provider-status observations and published incident history for HCP Terraform.

Operational

HCP Terraform is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow HCP Terraform for future changes.

89.5% of 57 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 83.3% 30 5

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

30 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources
minor Source not attested
Last archived state: resolved
View archived record details
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...
Issues When Downloading Terraform Providers
minor Source not attested
Last archived state: resolved
View archived record details
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 problems.
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 when we have more information.
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.
DR Cluster Creation Failures
Source not attested
Last archived state: resolved
View archived record details
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 workloads are not impacted. We will provide updates as more information becomes available.
Infragraph Snapshot are stuck
major Source not attested
Last archived state: resolved
View archived record details
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.
HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.
minor Source not attested
Last archived state: resolved
View archived record details
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.
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.
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 with more information as it becomes available.
Infragraph Service and UI down
critical Source not attested
Last archived state: resolved
View archived record details
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.
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.
HCP Terraform UI Not Loading
major Source not attested
Last archived state: resolved
View archived record details
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.
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 we have additional information, we will share another update.
July 2026
app.terraform.io is not loading
major Source not attested
Last archived state: resolved
View archived record details
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.
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.
HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade
major Source not attested
Last archived state: resolved
View archived record details
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.
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 information, we will share another update.
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.
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.
Increased Load Times for HCP Portal
Source not attested
Last archived state: resolved
View archived record details
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.
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.