Live

Remote Terraform runs failing

0

HashiCorp reports that remote execution Terraform runs queue or start slowly. HashiCorp is investigating the issue.

State

Investigating

Started

Ongoing for

58 min

Worst impact

Degraded

Timeline

1 update
10:5211:0611:2111:3511:49
DegradedUpdate postedTimes in UTC

Investigating

58 min 100%

Updates

Times in UTC

As posted by HashiCorp

Investigating

We are aware of and investigating reports of remote execution Terraform runs queuing or starting slowly. Our Engineering team is working to identify and resolve the issue. We will post updates with more information as it becomes available. **Next update time**: 12:00 AM UTC

HashiCorp in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

18

Median duration

2 h 43 min

This incident

65% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 days
median 2 h 43 min
90 days agoToday

Other HashiCorp incidents

All incidents

HashiCorp·Some of HCP Boundary Clusters might be seeing degraded performance.

Some HCP Boundary Clusters had degraded performance. A few customers had intermittent problems when they logged in to the Boundary console. HashiCorp reports that the issue is resolved and that it lasted 2 hours and 43 minutes.

Resolved

HashiCorp·Emergency Maintenance Notification – HCP Radar

Emergency maintenance on the HCP Radar service caused brief unavailability of billing, metering, and onboarding agent flows. HashiCorp reports that the maintenance is resolved and all services operate normally. The outage lasted about 6 hours and 5 minutes.

Resolved

HashiCorp·HYOK, Private VCS, and Private Run Tasks returning 403 errors

HashiCorp reports that requests through the tfc-agent return 403 errors. This affected HYOK, Private VCS, and Private Run Tasks. HashiCorp later reported that the service resumed 403 errors, and the team investigates again.

Resolved

HashiCorp·HCP Boundary Scheduled Maintenance

HCP Boundary service availability may be affected during scheduled maintenance on Saturday November 14th 2026, starting at 2:00 PM UTC. HashiCorp expects the work to take under 2 hours. The incident is resolved because the notice was posted for a future date.

Resolved

HashiCorp·HCP Terraform – Elevated 502 Bad Gateway Errors

HCP Terraform had 502 Bad Gateway errors that caused degraded performance for some customers. HashiCorp reports that the issue is resolved. The outage lasted about 111 minutes, from 08:13 to 10:04 UTC on 5 November 2026.

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane