Live / HashiCorp / Incident
HashiCorp: GitHub and Other VCS workloads experiencing intermittent issues
HashiCorp · hashicorp.comMajor incidentResolved2026-10-22 20:03 UTC
Public — what happened
Summary
HashiCorp said that starting at 17:15 UTC on 2026-10-22, workloads connected to version control systems, such as those used with Terraform, were failing intermittently. It first pointed to a problem GitHub had acknowledged with its API, then reported that some affected setups were not hosted on GitHub. By 19:22 UTC, HashiCorp said it had traced the problem to a particular tfc-agent release, rolled remote runs back to the earlier version, and advised people running their own agents to downgrade too. It also warned that Stacks users using proxies might see a regression on the older version, and the incident was marked resolved at 20:01 UTC.
Timeline
- Started — 2026-10-22 17:15 UTC
- Identified — 2026-10-22 17:15 UTC
- Investigating — 2026-10-22 17:32 UTC (2 updates)
- Monitoring — 2026-10-22 18:33 UTC
- Investigating — 2026-10-22 18:47 UTC
- Identified — 2026-10-22 19:22 UTC
- Resolved — 2026-10-22 20:01 UTC · 2h 45m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach HashiCorp against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for HashiCorp: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the HashiCorp report →
More from HashiCorp
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.