HashiCorp incident
HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.
HashiCorp experienced a minor incident on August 6, 2026 affecting HCP Terraform, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 05, 2026, 07:08 PM UTC
Status: 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. Affected components HCP Terraform (Degraded performance)
- identified Aug 05, 2026, 07:39 PM UTC
Status: 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. Affected components HCP Terraform (Degraded performance)
- monitoring Aug 05, 2026, 08:46 PM UTC
Status: 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. Affected components HCP Terraform (Degraded performance)
- resolved Aug 06, 2026, 08:33 PM UTC
Status: Resolved 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. Affected components HCP Terraform (Operational)