Skip to main content
Vendor reliability

Vendor record

HashiCorp Cloud

Vendor reports Operational

Checked

Front door check counts and HashiCorp Cloud’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We have no front door checks against HashiCorp Cloud in the last 30 days. That does not show whether it was reachable.

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every HashiCorp Cloud product, region or your app worked.

How we count front door checks

HashiCorp Cloud says

Incident posts from HashiCorp Cloud’s status page, with its titles, impact levels and times. They say what HashiCorp Cloud chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

2

incidents HashiCorp Cloud posted, last 7 days

All vendors’ incidents

Most recent records · all dates

  • HCP Terraform Scheduled Maintenance (2026-11-14)

    Not specified

    First seen by CheckUpstream

    Closed in our record

  • Terraform Runs Failing

    Not specified

    Started, per HashiCorp Cloud

    Closed in our record(28m)

  • HCP Vault Azure: Cluster Updates and Creation

    Not specified

    Started, per HashiCorp Cloud

    Closed in our record(5d 6h)

  • Users unable to access releases.hashicorp.con

    Major

    Started, per HashiCorp Cloud

    Closed in our record(57m)

    HashiCorp Cloud’s post
  • HCP Terraform Returning 404s

    Critical

    Started, per HashiCorp Cloud

    Closed in our record(2h 18m)

    HashiCorp Cloud’s post
12 older records
  • Hashicorp Linux packages GPG key rotation

    Major

    Started, per HashiCorp Cloud

    Closed in our record(7h 16m)

    HashiCorp Cloud’s post
  • Errors creating new VCS workspaces with Bitbucket cloud provider

    Minor

    Started, per HashiCorp Cloud

    Closed in our record(3h 54m)

    HashiCorp Cloud’s post
  • Delayed HCP Terraform Runs

    Minor

    Started, per HashiCorp Cloud

    Closed in our record(2d 19h)

    HashiCorp Cloud’s post
  • Issues When Downloading Terraform Providers

    Minor

    Started, per HashiCorp Cloud

    Closed in our record(1h 45m)

    HashiCorp Cloud’s post
  • DR Cluster Creation Failures

    Not specified

    Started, per HashiCorp Cloud

    Closed in our record(2h 40m)

    HashiCorp Cloud’s post
  • Infragraph Snapshot are stuck

    Major

    Started, per HashiCorp Cloud

    Closed in our record(1h 58m)

    HashiCorp Cloud’s post
  • HCP Terraform is unable to communicate with VCS endpoints using certain IP addresses.

    Minor

    Started, per HashiCorp Cloud

    Closed in our record(1d 1h)

    HashiCorp Cloud’s post
  • Infragraph Service and UI down

    Critical

    Started, per HashiCorp Cloud

    Closed in our record(27m)

    HashiCorp Cloud’s post
  • HCP Terraform UI Not Loading

    Major

    Started, per HashiCorp Cloud

    Closed in our record(1h 54m)

    HashiCorp Cloud’s post
  • app.terraform.io is not loading

    Major

    Started, per HashiCorp Cloud

    Closed in our record(2h 20m)

    HashiCorp Cloud’s post
  • HCP Terraform Workspace Runs Failing with IAM Errors After AWS Provider Upgrade

    Major

    Started, per HashiCorp Cloud

    Closed in our record(8h 7m)

    HashiCorp Cloud’s post
  • Increased Load Times for HCP Portal

    Not specified

    Started, per HashiCorp Cloud

    Closed in our record(15h 41m)

    HashiCorp Cloud’s post

Your code, your dependencies

See which of your code paths call HashiCorp Cloud

Connect GitHub or GitLab to find where your public or private repository uses HashiCorp Cloud. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add HashiCorp Cloud status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · HashiCorp CloudStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/hashicorp-cloud?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="HashiCorp Cloud status badge"></iframe>

Frequently Asked Questions

Is HashiCorp Cloud currently down?

HashiCorp Cloud's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did HashiCorp Cloud last have an outage?

The most recent closed incident record began earlier today and spans 2h 40m. The vendor reported an incident. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for HashiCorp Cloud?

No. CheckUpstream does not run front door checks against HashiCorp Cloud. The incident history on this page is what HashiCorp Cloud reported, not a measure of how often it was available.

How do I monitor HashiCorp Cloud in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

What does HashiCorp Cloud do?

HashiCorp Cloud is a cloud-hosted service from HashiCorp for using and managing its infrastructure automation products, including tools for provisioning, secret management, networking, and service coordination. It is typically used by developers, platform teams, and operations staff through a web dashboard and product APIs to run and oversee HashiCorp services in managed environments.

How does CheckUpstream track HashiCorp Cloud?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.