HashiCorp Outage History

HashiCorp experienced intermittent connection resets that disrupted Terraform operations during init, plan, and apply phases for 4.5 hours. The engineering team implemented a fix to resolve the connectivity issues. The incident was classified as minor and the service was restored with ongoing monitoring.

HCP Terraform experienced degraded performance for 38 minutes due to an unspecified issue. The engineering team implemented a fix to resolve the performance problems. The service was restored and monitored to ensure full resolution.

HCP Vault Dedicated customers experienced issues with disaster recovery cluster creation and management for 120.1 hours. Existing regional disaster recovery capabilities remained functional and unaffected during the incident. The team investigated the root cause while the service disruption was classified as minor impact.

HashiCorp's HCP Projects page experienced intermittent 404 errors and degraded performance for 1.5 hours. The engineering team identified the root cause and worked on implementing a fix. The issue has been resolved, restoring normal functionality to the Projects page.

HashiCorp's Boundary cluster console UI experienced accessibility issues for 1.7 hours, with new and existing Boundary sessions being blocked by an unhealthy internal service. The engineering team identified the root cause, deployed a fix, and implemented monitoring to ensure full resolution of the degraded performance.

HashiCorp's HCP web UI experienced intermittent issues for 2.1 hours, while backend services and APIs remained fully operational with jobs continuing to run normally. The engineering team identified the root cause and implemented a fix, then monitored the system to ensure full resolution.

HashiCorp's Vault Radar service experienced degraded performance for 56 minutes. The engineering team implemented a fix to resolve the performance issues and continued monitoring to ensure full resolution.

HashiCorp experienced a major outage where Terraform runs were not proceeding, with users reporting issues accessing resources from GitHub. The engineering team identified the root cause as 500 errors related to log upload and download functionality. The issue was resolved after 2 hours with a fix implemented to restore normal Terraform run operations.

HashiCorp's Terraform Cloud experienced 500 errors when users attempted to view Terraform run logs, lasting 6.1 hours. Terraform workloads continued to function normally, but run logs were only available for download after completion rather than being viewable in real-time. The engineering team identified the root cause and implemented a fix to restore normal log viewing functionality.