Live  /  HashiCorp  /  Incident

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

HashiCorp · hashicorp.comMajor incidentResolved2026-11-14 03:59 UTC
Public — what happened

Summary

HashiCorp said that starting at 03:23 UTC on 2026-11-14 it saw a higher-than-normal rate of 403 errors, which are access-denied responses, on requests passed through its tfc-agent. The company said this could affect HYOK, Private VCS, and Private Run Tasks, and rated the incident as major. Its engineers began investigating the cause, and the incident was marked resolved at 03:59, with no cause stated in the text provided.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 47, 2026, our weekly internet health report.

The full archive is on the HashiCorp status & history page.

Related: HashiCorp status & history. SquidGrid is not affiliated with HashiCorp.