HashiCorp experienced a minor incident on June 22, 2026 affecting AWS-ap-southeast-2 and Azure-UK South and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 22, 2026, 04:55 AM UTC
Status: Investigating We are aware of the issue that the cluster. creation is failing. We are actively investigating the issue. Our team is working to identify and resolve the issue. We will post updates with more information as it becomes available. Affected components Azure-UK South (Degraded performance) Azure-North Europe (Degraded performance) Azure-East US 2 (Degraded performance) AWS-eu-west-1 (Degraded performance) Azure-West Europe (Degraded performance) AWS-us-west-2 (Degraded performance) AWS-ap-northeast-1 (Degraded performance) Azure-Canada Central (Degraded performance) Azure-Central US (Degraded performance) AWS-us-east-2 (Degraded performance) Azure-East US (Degraded performance) AWS-us-east-1 (Degraded performance) Azure-West US 2 (Degraded performance) Azure-Japan East (Degraded performance) Azure-Canada East (Degraded performance) AWS-ap-southeast-2 (Degraded performance) AWS-ca-central-1 (Degraded performance) AWS-eu-west-2 (Degraded performance) Azure-Southeast Asia (Degraded performance) AWS-ap-southeast-1 (Degraded performance) Azure-France Central (Degraded performance) Azure-Australia Southeast (Degraded performance) AWS-eu-central-1 (Degraded performance)
- identified Jun 22, 2026, 07:01 AM UTC
Status: Identified Our Engineering team has identified the cause to be a a CI build-number drift between app-image and terraform-image jobs in the same workflow run caused the service to reference a non-existent terraform image tag. We are actively working on a fix. Once we have additional information, we will share another update. Affected components AWS-ap-southeast-1 (Degraded performance) Azure-Japan East (Degraded performance) Azure-West Europe (Degraded performance) AWS-us-west-2 (Degraded performance) AWS-ap-northeast-1 (Degraded performance) AWS-us-east-2 (Degraded performance) Azure-East US (Degraded performance) Azure-West US 2 (Degraded performance) Azure-East US 2 (Degraded performance) Azure-Australia Southeast (Degraded performance) AWS-eu-central-1 (Degraded performance) AWS-eu-west-2 (Degraded performance) Azure-Southeast Asia (Degraded performance) Azure-Canada Central (Degraded performance) Azure-Central US (Degraded performance) Azure-France Central (Degraded performance) AWS-eu-west-1 (Degraded performance) Azure-Canada East (Degraded performance) AWS-ap-southeast-2 (Degraded performance) Azure-North Europe (Degraded performance) Azure-UK South (Degraded performance) AWS-ca-central-1 (Degraded performance) AWS-us-east-1 (Degraded performance)
- resolved Jun 22, 2026, 08:10 AM 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 Azure-Central US (Operational) Azure-East US 2 (Operational) Azure-France Central (Operational) AWS-us-west-2 (Operational) Azure-Australia Southeast (Operational) AWS-eu-west-2 (Operational) Azure-North Europe (Operational) Azure-Canada Central (Operational) AWS-ap-southeast-1 (Operational) Azure-Japan East (Operational) AWS-us-east-2 (Operational) Azure-Canada East (Operational) Azure-UK South (Operational) Azure-West Europe (Operational) AWS-ap-northeast-1 (Operational) AWS-eu-central-1 (Operational) AWS-ca-central-1 (Operational) AWS-us-east-1 (Operational) AWS-eu-west-1 (Operational) AWS-ap-southeast-2 (Operational) Azure-East US (Operational) Azure-West US 2 (Operational) Azure-Southeast Asia (Operational)