HashiCorp incident
Startup issues for self-hosted Terraform agents after version update.
HashiCorp experienced a minor incident on May 13, 2026 affecting HCP Terraform, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 13, 2026, 05:17 AM UTC
Status: Investigating We are aware of and investigating reports of issues in starting up self hosted TFC agents which cause run failures in Terraform cloud workspaces. Our team is working to identify and resolve the issue. Please refer to this KB article for symptoms and workaround - https://www.ibm.com/support/pages/node/7272788 Affected components HCP Terraform (Degraded performance)
- identified May 13, 2026, 05:08 PM UTC
Status: Identified We have identified the issue and are working on a fix for self-hosted HCP Terraform agents failing to start when auto-upgrading from 1.28.6+ to 1.28.9, causing run failures in HCP Terraform workspacesOur team is working to identify and resolve the issue. Please refer to this KB article for symptoms and workarounds until the fix is released - https://www.ibm.com/support/pages/node/7272788 Affected components HCP Terraform (Degraded performance)
- monitoring May 13, 2026, 09:17 PM UTC
Status: Monitoring We have released a fix for self-hosted HCP Terraform agents failing to start when auto-upgrading from 1.28.6+. Automatic updates will now upgrade to 1.28.10. Affected components HCP Terraform (Degraded performance)
- resolved May 13, 2026, 09:55 PM UTC
Status: Resolved We have resolved issues with self-hosted HCP Terraform agents failing to start when auto-upgrading from 1.28.6+. If you continue to experience problems, please open a ticket with our support team. Affected components HCP Terraform (Operational)