Loading status…
Loading status…
HashiCorp status · Cloud & Infrastructure · checked (0s ago)
Also searched as Terraform, HCP Terraform, Terraform Cloud, Terraform Registry, Vault, Consul, Nomad.
No — HashiCorp is not down. All HashiCorp systems are reported operational.
According to HashiCorp's official status page, HashiCorp was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, HashiCorp's feed reported no outage in 100.00% of our checks.
Everything above is read from HashiCorp's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported HashiCorp in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
HashiCorp builds Terraform, Vault, Consul, Nomad, Packer and Vagrant, and runs the hosted versions: HCP Terraform (formerly Terraform Cloud), HCP Vault and the public Terraform Registry that `terraform init` downloads providers from.
The status page covers the hosted services and the registry separately. The registry is the component with the widest blast radius: it is not part of anyone's running infrastructure, but when it is unavailable every `terraform init` in the world that needs an uncached provider fails, including in CI.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where HashiCorp's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days HashiCorp was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 0s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of HashiCorp's status endpoint.
HashiCorp has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what HashiCorp posted itself — not every problem users hit.
resolved · Sep 16, 05:41 PM (6d ago)
resolved · Sep 10, 01:24 PM (13d ago)
resolved · Sep 4, 05:51 PM (18d ago)
resolved · Aug 15, 05:08 PM (39d ago)
resolved · Aug 13, 05:50 PM (40d ago)
resolved · Aug 12, 09:28 PM (41d ago)
resolved · Aug 6, 08:40 AM (48d ago)
resolved · Aug 5, 08:09 PM (48d ago)
resolved · Aug 5, 07:08 PM (48d ago)
resolved · Aug 5, 03:11 PM (49d ago)
resolved · Aug 5, 12:05 AM (49d ago)
resolved · Jul 30, 11:06 PM (54d ago)
resolved · Jul 29, 12:36 PM (56d ago)
resolved · Jul 29, 12:09 AM (56d ago)
resolved · Jul 21, 10:32 AM (64d ago)
resolved · Jul 7, 01:58 PM (78d ago)
resolved · Jun 30, 12:16 PM (85d ago)
resolved · Jun 30, 06:50 AM (85d ago)
resolved · Jun 25, 04:57 PM (90d ago)
resolved · Jun 22, 04:55 AM (93d ago)
A failing `terraform init` may be a provider version constraint or a private module source rather than the registry — read the error rather than assuming. State lock errors are a stuck lock from an interrupted run, not an outage. Vault returning 403 is usually an expired token or a policy change, and a sealed Vault is a deliberate state, not a failure.
HashiCorp is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.