HashiCorp reports normal operation on its official status page.

How often does HashiCorp have incidents?

HashiCorp reported 16 incidents in the last 90 days, on 21 different days.

HashiCorp

HashiCorp is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 29 min

Longest incident

5 days

Components

HCP Portal Operational

90 days agoNo incidentsToday

HCP API Operational

90 days agoNo incidentsToday

HCP Boundary Operational

90 days agoNo incidentsToday

AWS-ap-northeast-1 Operational

90 days agoNo incidentsToday

AWS-ap-southeast-1 Operational

90 days agoNo incidentsToday

AWS-ap-southeast-2 Operational

90 days agoNo incidentsToday

AWS-ca-central-1 Operational

90 days agoNo incidentsToday

AWS-eu-central-1 Operational

90 days agoNo incidentsToday

AWS-eu-west-1 Operational

90 days agoNo incidentsToday

AWS-eu-west-2 Operational

90 days agoNo incidentsToday

AWS-us-east-1 Operational

90 days agoNo incidentsToday

AWS-us-east-2 Operational

90 days agoNo incidentsToday

AWS-us-west-2 Operational

90 days agoNo incidentsToday

Azure-Australia Southeast Operational

90 days agoNo incidentsToday

Azure-Canada Central Operational

90 days agoNo incidentsToday

Azure-Central US Operational

90 days agoNo incidentsToday

Azure-East US Operational

90 days agoNo incidentsToday

Azure-East US 2 Operational

90 days agoNo incidentsToday

Azure-France Central Operational

90 days agoNo incidentsToday

Azure-Japan East Operational

90 days agoNo incidentsToday

Azure-North Europe Operational

90 days agoNo incidentsToday

Azure-Southeast Asia Operational

90 days agoNo incidentsToday

Azure-UK South Operational

90 days agoNo incidentsToday

Azure-West Europe Operational

90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 22, 2026

Duration2 h 45 min17:15 to 20:01GitHub and Other VCS workloads experiencing intermittent issuesPartial outage

Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect. We've patched the bug in git. If you are using remote runs, you don't have to do anything, you're already on 1.33.3. If you downgraded to 1.33.1 to work around git-based VCS problems, you can safely upgrade to 1.33.3 now. Please contact support if you experience any further issues.status.hashicorp.com

Oct 13, 2026

Duration22 min16:01 to 16:23Terraform Runs FailingPartial outage

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.status.hashicorp.com

Oct 4, 2026

Duration5 days00:38 to 06:43HCP Vault Azure: Cluster Updates and CreationNotice

Sep 26, 2026

Duration57 min02:06 to 03:03Users unable to access releases.hashicorp.conPartial outage

Sep 23, 2026

Duration2 h 19 min17:43 to 20:02HCP Terraform Returning 404sMajor outage

Sep 16, 2026

Duration4 h 40 min17:41 to 22:21Degraded commit/content scans in HCP Vault RadarDegraded

Sep 10, 2026

Duration7 h 17 min13:24 to 20:40Hashicorp Linux packages GPG key rotationPartial outage

Sep 4, 2026

Duration3 h 54 min17:51 to 21:46Errors creating new VCS workspaces with Bitbucket cloud providerDegraded

Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to experience any problems, please open a ticket with our support team.status.hashicorp.com

Aug 15, 2026

Duration3 days17:08 to 12:50Delayed HCP Terraform RunsDegraded

Aug 13, 2026

Duration1 h 16 min17:50 to 19:06Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resourcesDegraded

Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.status.hashicorp.com

Aug 12, 2026

Duration1 h 46 min21:28 to 23:14Issues When Downloading Terraform ProvidersDegraded

3rd party provider downloads are confirmed to be functioning. Please retry any failed Terraform runs, and contact support if you have any further problems.status.hashicorp.com

Aug 6, 2026

Duration2 h 40 min08:40 to 11:20DR Cluster Creation FailuresNotice

We have implemented a mitigation for the issue affecting new Disaster Recovery (DR) cluster creation. Initial validation has been successful, and new DR cluster creation is functioning as expected. We are continuing to monitor the service to ensure stability before considering the incident fully resolved.status.hashicorp.com

Maintenance

HCP Terraform Scheduled Maintenance

HCP Terraform and HCP Waypoint will undergo scheduled maintenance on Saturday December 5th 2026, beginning at 17:00 UTC. This maintenance is necessary to improve performance and increase capacity. We expect this maintenance to complete in under 2.5 hours. These services will be unavailable until maintenance completes. Customers will not be able to manually or automatically trigger Terraform operations during maintenance. Updates will be posted as necessary throughout the maintenance period. (This maintenance was [previously posted here](https://status.hashicorp.com/incidents/01M52FDG50DQQAGSJGJBMTK6M1), but has been re-posted to ensure customers are notified of the change in time.)

Maintenanceupdated 4 d ago

Follow HashiCorp

Your coding agent knows when HashiCorp is down, and tells you when a failure is theirs, not yours. You can also get HashiCorp incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "hashicorp" and tell me if HashiCorp has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=hashicorp

Slack

/feed subscribe https://outages.live/feed.xml?providers=hashicorp

Go from tracking outages to fixing production issues with Polylane.

Try Polylane