Vendor Status Watch

← all vendors

Hashicorp status history

Current state: operational — “All Systems Operational” per https://status.hashicorp.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

2incidents, last 30 days
20incidents, last 90 days
27incidents on record
Incidents per week, last 12 weeks:
Get Hashicorp alerts in your Slack — free templateRSS for Hashicorp

How long do Hashicorp incidents last?

2.7 hmedian incident duration27 measured
22.9 h90th percentile1 in 10 ran longer
2.3 hmedian, major/critical only7 incidents

From 27 incidents with a vendor-posted start and resolve time. Longest on record: Delayed HCP Terraform Runs — 2.8 days (2026-08-15 17:08 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (27)

StartedIncidentStatusImpactDuration
2026-09-10 13:24 UTCHashicorp Linux packages GPG key rotationresolvedmajor7 h 16 min
2026-09-04 17:51 UTCErrors creating new VCS workspaces with Bitbucket cloud providerresolvedminor3 h 54 min
2026-08-15 17:08 UTCDelayed HCP Terraform Runsresolvedminor2 d 19 h
2026-08-13 17:50 UTCTerraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resourcesresolvedminor1 h 15 min
2026-08-12 21:28 UTCIssues When Downloading Terraform Providersresolvedminor1 h 45 min
2026-08-06 08:40 UTCDR Cluster Creation Failuresresolvednone2 h 40 min
2026-08-05 20:09 UTCInfragraph Snapshot are stuckresolvedmajor1 h 58 min
2026-08-05 19:08 UTCHCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.resolvedminor25 h 25 min
2026-08-05 15:11 UTCInfragraph Service and UI downresolvedcritical27 min
2026-08-05 00:05 UTCHCP Terraform UI Not Loadingresolvedmajor1 h 54 min
2026-07-30 23:06 UTCapp.terraform.io is not loadingresolvedmajor2 h 20 min
2026-07-29 12:36 UTCHCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgraderesolvedmajor8 h 07 min
2026-07-29 00:09 UTCIncreased Load Times for HCP Portalresolvednone15 h 41 min
2026-07-21 10:32 UTCTerraform Runs Failing to Fetch GitHub Sources Over SSHresolvedminor2 h 11 min
2026-07-07 13:58 UTCIntermittent Bitbucket Data Center VCS Triggered Terraform run Failuresresolvednone7 h 54 min
2026-06-30 12:16 UTCTerraform releases page experiencing errorsresolvedminor43 min
2026-06-30 06:50 UTCCluster Provisioning and Management Operations Impactedresolvednone1 h 17 min
2026-06-25 16:57 UTCIntermittent 5XX errors for registryresolvedminor1 h 18 min
2026-06-22 04:55 UTCCluster Creation Is Failingresolvedminor3 h 15 min
2026-06-18 23:54 UTCTerraform Provider Azure RMresolvedminor22 h 51 min
2026-06-17 05:47 UTCIssues Re-enabling SAML connectionsresolvedminor1 h 12 min
2026-06-16 18:29 UTCVault Radarresolvedminor45 h 47 min
2026-06-15 16:13 UTCTerraform Registry Degradedresolvedminor6 h 10 min
2026-06-11 19:33 UTCDownloading Terraform State Filesresolvedminor1 h 47 min
2026-06-10 22:44 UTCHCP Terraform Authenticationresolvedminor1 h 56 min
2026-05-15 14:43 UTCUnable to Fetch Packages via apt.releases.hashicorp.comresolvedcritical8 h 19 min
2026-05-13 05:17 UTCStartup issues for self-hosted Terraform agents after version update.resolvedminor16 h 37 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Hashicorp with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "hashicorp"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}