HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.
Aug 5, 19:08 UTCAug 6, 20:33 UTC
Duration
25h 25m
Impact
Minor
Root cause
Not disclosed
HashiCorp, 90 days
13 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Aug 6, 20:33 UTC
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.
- Monitoring · Aug 5, 20:46 UTC
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 · Aug 5, 19:39 UTC
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 · Aug 5, 19:08 UTC
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.
More from HashiCorp
Full historyHCP Boundary Scheduled Maintenancelasted 7mHCP Terraform – Elevated 502 Bad Gateway Errorslasted 1h 51mGitHub and Other VCS workloads experiencing intermittent issueslasted 2h 45mTerraform Runs Failinglasted 22mHCP Vault Azure: Cluster Updates and Creationlasted 5d 6hUsers unable to access releases.hashicorp.conlasted 57m