CompaniesdevtoolsTerraform Cloud (HCP)
Terraform Cloud (HCP)
developer.hashicorp.com (opens in new tab)Status page (opens in new tab)Pricing page (opens in new tab)
Is Terraform Cloud (HCP) down?
Terraform Cloud (HCP)’s status page reports all systems operational since , as of our latest poll (every 10 minutes).
Last incident: HCP Boundary Scheduled Maintenance, started , resolved . 4 incidents in the last 30 days, 13 in 90. Status history · Uptime
Follow Terraform Cloud (HCP): Atom feed, calendar, or start a stack with it to follow it alongside your other vendors.
- Status page says
- Operational since
- Last 90 days
- 13 incidents, 6 major or critical
- Rewrites caught
- 3 edited
- Next deprecation
- None announced
Select a day to jump to its incidents below. Days are in UTC.
How Terraform Cloud (HCP) reports incidents
Not enough incidents to compare Terraform Cloud (HCP) with other vendors yet: a vendor needs 20 incidents in a year and 10 with full update detail (Terraform Cloud (HCP) has 22 and 22).
Provisional. Built nightly from every archived version of each incident, last on . Compare all vendors
Dependencies
What Terraform Cloud (HCP) relies on and who relies on Terraform Cloud (HCP), as observed in status-page incidents: who they blame, where they say they run, and who fails at the same time. Observed, not verified.
Terraform Cloud (HCP) depends on
| Provider | Evidence | Signal |
|---|---|---|
| GitHub | blamed in 2 incidents; integration affected in 1; together in 1 outage event “…contact support if you have any further problems. 3rd-party Terraform providers hosted on GitHub are experiencing download issues. Official providers are unaffected. GitHub is investigating the proble…” incident | Strong |
| Bitbucket | integration affected in 1 “…Errors creating new VCS workspaces with Bitbucket cloud provider Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to expe…” incident | Weak |
Outage events: GitHub, .
Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.
Changes and edits
Incidents Terraform Cloud (HCP) rewrote or removed, and notable changes to the pages we watch.
Struck in red is what Terraform Cloud (HCP) removed. Blue is what they added.
YesterdayFriday, November 6Fri, Nov 6
1 incident change
- MaintenanceMajor incident
Thursday, November 5
1 rewrite
- Duration shortenedEdited by the vendor
HCP Terraform – Elevated 502 Bad Gateway Errors
Start time
08:1309:04 UTC
Friday, October 23
1 rewrite
- Minor editEdited by the vendor
HCP Terraform Scheduled Maintenance
Start time
Nov 14 17:00Dec 5 17:00 UTC
Thursday, October 22
1 rewrite, 1 incident change
- Wording onlyEdited by the vendor
GitHub and Other VCS workloads experiencing intermittent issues
Update text …http://GitHub.com Next update time:
17:3018:00 UTC - DegradationMajor incident
GitHub VCS workloads experiencing intermittent issues
Terraform Cloud reported a major degradation affecting GitHub VCS workloads starting 2026-10-22 17:15 UTC. GitHub acknowledged intermittent API access issues that could cause VCS-based Terraform workloads to malfunction; Terraform Cloud was monitoring GitHub and awaiting updates. The incident was still open when archived, open for 0 min at the last update.
Tuesday, October 13
1 incident change
- OutageMajor incident
Terraform Cloud (HCP) reported a major incident affecting some customers: Terraform applies failed with a pre-apply run task error, “Unexpected response from broker: Status code: 424, Message: Failed Dependency.” It started at 2026-10-13 16:01 UTC and lasted 22 min, resolving at 2026-10-13 16:23 UTC after Engineering implemented a fix.
Saturday, September 26
1 incident change
- OutageMajor incident
Users unable to access releases.hashicorp.con
A major outage prevented access to releases.hashicorp.com, causing 504 errors and affecting terraform provider downloads and Vault Radar access. The recorded incident started at 2026-09-26 02:35 UTC and lasted 28 min, resolving at 2026-09-26 03:03 UTC; engineering reported implementing a fix.
Wednesday, September 23
1 incident change
- OutageCritical incident
HCP Terraform returned 404s and experienced degraded performance in a critical incident starting 2026-09-23 17:43 UTC. A fix was implemented at 09-23 18:06 UTC, and the incident was resolved at 2026-09-23 20:02 UTC after 2 h 18 min; the vendor reported systems operating normally.
Thursday, September 10
1 incident change
- DegradationMajor incident
Hashicorp Linux packages GPG key rotation
HashiCorp reported a major Linux package-signing degradation: the published GPG fingerprint was outdated and could mismatch the active key, affecting package verification. The incident ran from 2026-09-10 13:24 UTC to 2026-09-10 20:40 UTC (7 h 16 min). HashiCorp updated apt/rpm repository keys and documentation, worked to re-sign older-key packages, and reported resolution.
Wednesday, August 5
1 incident change
- DegradationMajor incident
Terraform Cloud (HCP) reported stuck Infragraph snapshots and degraded performance, with major impact, starting 2026-08-05 20:09 UTC. The incident lasted 1 h 58 min and was resolved at 2026-08-05 22:08 UTC; engineering said systems should be operating normally, but provided no cause or specific fix.
Recent CVEs
Published vulnerabilities in Terraform Cloud (HCP)’s software or packages. Not a statement that the hosted service was exposed.
Pricing and pages we watch
| Page | Versions | Last changed | Last checked | History |
|---|---|---|---|---|
| Pricing page (opens in new tab)partial | 0 | No changes yet |
Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.
The Weekly Rewind: one short weekly email on what changed at Terraform Cloud (HCP) and the other vendors we track, including silent edits. Subscribe (opens in new tab)
Incidents
22 incidents since Jul 21, 11 of them major or critical. Maintenance is left out.
YesterdayFriday, November 6Fri, Nov 6
1 incident, 1 major or critical
- Major, 7 minMajor incident
Thursday, November 5
1 incident
- Minor, 1 hMinor incident
Thursday, October 22
1 incident, 1 major or critical
- Major, 27 h 52 minMajor incident
Tuesday, October 13
1 incident, 1 major or critical
- Major, 22 minMajor incident
Sunday, October 4
1 incident
- No impact listed, 5 daysIncident, no impact listed
Saturday, September 26
1 incident, 1 major or critical
- Major, 28 minMajor incident
Wednesday, September 23
1 incident, 1 major or critical
- Critical, 2 h 19 minCritical incident
Wednesday, September 16
1 incident
- Minor, 4 h 40 minMinor incident
Thursday, September 10
1 incident, 1 major or critical
- Major, 7 h 17 minMajor incident
Friday, September 4
1 incident
- Minor, 3 h 54 minMinor incident
Saturday, August 15
1 incident
- Minor, 3 daysMinor incident
Thursday, August 13
1 incident
- Minor, 1 h 16 minMinor incident
Wednesday, August 12
1 incident
- Minor, 1 h 46 minMinor incident
Thursday, August 6
1 incident
- No impact listed, 2 h 43 minIncident, no impact listed
Wednesday, August 5
4 incidents, 3 major or critical
- Major, 1 h 59 minMajor incident
- Minor, 25 h 25 minMinor incident
- Critical, 27 minCritical incident
- Major, 1 h 54 minMajor incident
Thursday, July 30
1 incident, 1 major or critical
- Major, 2 h 21 minMajor incident
Wednesday, July 29
2 incidents, 1 major or critical
- Major, 8 h 8 minMajor incident
- No impact listed, 15 h 41 minIncident, no impact listed
Tuesday, July 21
1 incident
- Minor, 2 h 12 minMinor incident