HASHICORP

🟠 DNS resolution decided to play hide-and-seek with HCP Terraform, causing intermittent outages. HashiCorp's team found the culprit and is now performing emergency surgery. Your infrastructure's GPS is temporarily broken. (Auto-resolved: no updates in 24h)

⏰ Feb 10, 2026 Fixed (for now) spotted via status_rss

// The official story

Intermittent issues with HCP Terraform

// Status page says

Status: Identified Our Engineering team has identified a DNS resolution issue as the cause and we are actively working on a fix. Once we have additional information, we will share another update. Affected components HCP Terraform (Partial outage)

🔗 Official status page (for the PR-approved version)

https://status.hashicorp.com//incidents/01KH4NDGQ0GMQBWXF188WNDG2S

Hashicorp's Greatest Hits

🔴 HASHICORP 3h ago

🟠 HCP Terraform is partially down and choking on runs. Engineering deployed a fix and are now in the 'monitoring' phase, which is code for 'fingers crossed and refreshing dashboards every 30 seconds.' Infrastructure as Code? More like Infrastructure as Chaos right now.

🟢 HASHICORP Sep 26, 2026

🟡 HashiCorp's release CDN is serving up 504s instead of Terraform providers. Vault Radar also ghosted the party. Engineering team is currently at the 'staring at logs' phase of debugging. (Auto-resolved: no updates in 24h)

🟢 HASHICORP Sep 23, 2026

🟡 HashiCorp's Terraform is throwing 404s like it forgot what it manages. Your infrastructure declarations are apparently filing for missing persons reports. Team's investigating, but your deploys are currently experiencing an existential crisis. (Auto-resolved: no updates in 24h)

🟢 HASHICORP Sep 10, 2026

🟠 HashiCorp rotated Linux package signing keys and forgot to tell half their infrastructure. APT and RPM repos are now selectively trusting packages like a teenager with trust issues. Engineers are manually re-signing everything because automation apparently doesn't work on Tuesdays. (Auto-resolved: no updates in 24h)