Skip to service list
IU
HashiCorp

Is HashiCorp down?

HashiCorp status · Cloud & Infrastructure · checked (1s ago)

Also searched as Terraform, HCP Terraform, Terraform Cloud, Terraform Registry, Vault, Consul, Nomad.

Operational

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 99.94% of our checks.

No outage reported (30d)
99.94%
Share of our checks where HashiCorp's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
841 ms
How long the last status check took
Reported by
Operational
All Systems Operational

Is HashiCorp down for you right now?

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.

What HashiCorp is

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.

What HashiCorp's status feed covers

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.

HashiCorp uptime, last 30 days

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.

2026-10-0913 of 30 days recordedToday
  • No outage reported (99%+)
  • 95–99%
  • 80–95%
  • Under 80%
  • No data

Other services reporting problems right now

9 other services isuptime tracks were also reporting a problem as of the same check, 1s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.

1 more service is reporting problems — see all →

HashiCorp response time trend

Each point is one check of HashiCorp's status endpoint.

HashiCorp outage history

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.

HashiCorp status — frequently asked

Is HashiCorp down right now?
No — HashiCorp is not down. All HashiCorp systems are reported operational. Checked (1s ago).
What is HashiCorp's status right now?
HashiCorp is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 841 ms. isuptime reads this from HashiCorp's own published feed and does not test HashiCorp independently.
When did HashiCorp last go down?
The most recent incident HashiCorp published was “HCP Boundary Scheduled Maintenance”, opened Nov 6, 03:09 PM UTC (1d ago) and marked resolved Nov 6, 03:15 PM UTC. That is the latest entry in HashiCorp's own incident feed, not every problem users experienced.
What is HashiCorp's uptime?
isuptime does not measure HashiCorp's uptime directly — it reads HashiCorp's own published status feed. Over the last 30 days, HashiCorp's own status feed reported no outage in 99.94% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is HashiCorp down for everyone?
HashiCorp reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.

HashiCorp says operational but it is not working for me

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.

Open HashiCorp's official status page

Alternatives to HashiCorp

HashiCorp is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.

If HashiCorp goes down

Status shown for each is read from that provider's own feed, on the same schedule as this page.

Other Cloud & Infrastructure services

← See live status for all 102 services