Skip to content

Outage tracker / HashiCorp Cloud

Is HashiCorp Cloud down?

I'm having a problem

Vendor reports no incidentWhat HashiCorp Cloud reports

HashiCorp Cloud reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:14 UTC.

HashiCorp Cloud's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 7 minutes ago

Our checks of HashiCorp Cloud pass from all 10 regions we check.

As of Nov 5, 2026, 2:26 PM UTC, RealUptime's checks of HashiCorp Cloud passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:26 PM UTC
US-East1052 msChecks passing
US-West846 msChecks passing
Europe191 msChecks passing
Asia-Pacific1576 msChecks passing
US-Central68 msChecks passing
Canada366 msChecks passing
UK90 msChecks passing
Southeast Asia327 msChecks passing
Australia372 msChecks passing
South America217 msChecks passing
their status pagetheir claim, not our reading

HashiCorp Cloud reports: All systems operational (“All Systems Operational”)

from HashiCorp Cloud's own status page, checked Nov 5, 2026, 1:57 PM UTC
HashiCorp Cloud's own status page shows no incident, and our checks of HashiCorp Cloud pass right now.

HashiCorp Cloud's own component breakdown, as they publish it

  • HCP PortalOperational
  • HCP APIOperational
  • HCP BoundaryOperational
  • AWS-ap-northeast-1Operational
  • AWS-ap-southeast-1Operational
  • AWS-ap-southeast-2Operational
  • AWS-ca-central-1Operational
  • AWS-eu-central-1Operational
  • AWS-eu-west-1Operational
  • AWS-eu-west-2Operational
  • AWS-us-east-1Operational
  • AWS-us-east-2Operational
  • AWS-us-west-2Operational
  • Azure-Australia SoutheastOperational
  • Azure-Canada CentralOperational
  • Azure-Central USOperational
  • Azure-East USOperational
  • Azure-East US 2Operational
  • Azure-France CentralOperational
  • Azure-Japan EastOperational
  • Azure-North EuropeOperational
  • Azure-Southeast AsiaOperational
  • Azure-UK SouthOperational
  • Azure-West EuropeOperational
  • Azure-West US 2Operational

These are HashiCorp Cloud's components, named and scored by HashiCorp Cloud. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is HashiCorp Cloud's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

HashiCorp Cloud response time, by region

US-East
2.1sp95 · latest
2.5s1.3s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 593ms2026-10-08 UTC: p95 623ms2026-10-09 UTC: p95 528ms2026-10-10 UTC: p95 768ms2026-10-11 UTC: p95 884ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 487ms2026-10-14 UTC: p95 390ms2026-10-15 UTC: p95 468ms2026-10-16 UTC: p95 723ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 905ms2026-10-19 UTC: p95 880ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.2s2026-10-23 UTC: p95 468ms2026-10-24 UTC: p95 378ms2026-10-25 UTC: p95 391ms2026-10-26 UTC: p95 476ms2026-10-27 UTC: p95 718ms2026-10-28 UTC: p95 942ms2026-10-29 UTC: p95 845ms2026-10-30 UTC: p95 798ms2026-10-31 UTC: p95 725ms2026-11-01 UTC: p95 910ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
US-West
2.3sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 828ms2026-10-08 UTC: p95 873ms2026-10-09 UTC: p95 834ms2026-10-10 UTC: p95 877ms2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 831ms2026-10-13 UTC: p95 597ms2026-10-14 UTC: p95 696ms2026-10-15 UTC: p95 715ms2026-10-16 UTC: p95 692ms2026-10-17 UTC: p95 756ms2026-10-18 UTC: p95 646ms2026-10-19 UTC: p95 722ms2026-10-20 UTC: p95 666ms2026-10-21 UTC: p95 786ms2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 522ms2026-10-24 UTC: p95 611ms2026-10-25 UTC: p95 506ms2026-10-26 UTC: p95 717ms2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 594ms2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 806ms2026-11-02 UTC: p95 2.5s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.3s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 436ms2026-10-09 UTC: p95 466ms2026-10-10 UTC: p95 412ms2026-10-11 UTC: p95 391ms2026-10-12 UTC: p95 419ms2026-10-13 UTC: p95 394ms2026-10-14 UTC: p95 380ms2026-10-15 UTC: p95 695ms2026-10-16 UTC: p95 383ms2026-10-17 UTC: p95 427ms2026-10-18 UTC: p95 370ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 910ms2026-10-21 UTC: p95 974ms2026-10-22 UTC: p95 971ms2026-10-23 UTC: p95 572ms2026-10-24 UTC: p95 409ms2026-10-25 UTC: p95 417ms2026-10-26 UTC: p95 471ms2026-10-27 UTC: p95 981ms2026-10-28 UTC: p95 545ms2026-10-29 UTC: p95 458ms2026-10-30 UTC: p95 779ms2026-10-31 UTC: p95 433ms2026-11-01 UTC: p95 412ms2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
1.6sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 940ms2026-10-08 UTC: p95 842ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 787ms2026-10-13 UTC: p95 871ms2026-10-14 UTC: p95 859ms2026-10-15 UTC: p95 771ms2026-10-16 UTC: p95 662ms2026-10-17 UTC: p95 894ms2026-10-18 UTC: p95 793ms2026-10-19 UTC: p95 774ms2026-10-20 UTC: p95 904ms2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 755ms2026-10-24 UTC: p95 1.8s2026-10-25 UTC: p95 1.2s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 2.9s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 914ms2026-11-02 UTC: p95 2.9s2026-11-03 UTC: p95 2.3s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-Central
691msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 428ms2026-10-08 UTC: p95 502ms2026-10-09 UTC: p95 658ms2026-10-10 UTC: p95 519ms2026-10-11 UTC: p95 464ms2026-10-12 UTC: p95 794ms2026-10-13 UTC: p95 671ms2026-10-14 UTC: p95 542ms2026-10-15 UTC: p95 453ms2026-10-16 UTC: p95 444ms2026-10-17 UTC: p95 414ms2026-10-18 UTC: p95 511ms2026-10-19 UTC: p95 449ms2026-10-20 UTC: p95 917ms2026-10-21 UTC: p95 674ms2026-10-22 UTC: p95 668ms2026-10-23 UTC: p95 845ms2026-10-24 UTC: p95 552ms2026-10-25 UTC: p95 613ms2026-10-26 UTC: p95 592ms2026-10-27 UTC: p95 699ms2026-10-28 UTC: p95 509ms2026-10-29 UTC: p95 399ms2026-10-30 UTC: p95 849ms2026-10-31 UTC: p95 928ms2026-11-01 UTC: p95 632ms2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 339ms2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 691ms
Oct 7Oct 21Nov 5
Canada
649msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 497ms2026-10-08 UTC: p95 486ms2026-10-09 UTC: p95 489ms2026-10-10 UTC: p95 438ms2026-10-11 UTC: p95 493ms2026-10-12 UTC: p95 570ms2026-10-13 UTC: p95 550ms2026-10-14 UTC: p95 524ms2026-10-15 UTC: p95 616ms2026-10-16 UTC: p95 615ms2026-10-17 UTC: p95 877ms2026-10-18 UTC: p95 996ms2026-10-19 UTC: p95 566ms2026-10-20 UTC: p95 554ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 800ms2026-10-23 UTC: p95 582ms2026-10-24 UTC: p95 517ms2026-10-25 UTC: p95 605ms2026-10-26 UTC: p95 710ms2026-10-27 UTC: p95 749ms2026-10-28 UTC: p95 684ms2026-10-29 UTC: p95 544ms2026-10-30 UTC: p95 578ms2026-10-31 UTC: p95 435ms2026-11-01 UTC: p95 482ms2026-11-02 UTC: p95 1.1s2026-11-03 UTC: p95 857ms2026-11-04 UTC: p95 756ms2026-11-05 UTC: p95 649ms
Oct 7Oct 21Nov 5
UK
295msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 283ms2026-10-08 UTC: p95 323ms2026-10-09 UTC: p95 389ms2026-10-10 UTC: p95 281ms2026-10-11 UTC: p95 382ms2026-10-12 UTC: p95 486ms2026-10-13 UTC: p95 511ms2026-10-14 UTC: p95 546ms2026-10-15 UTC: p95 434ms2026-10-16 UTC: p95 317ms2026-10-17 UTC: p95 315ms2026-10-18 UTC: p95 358ms2026-10-19 UTC: p95 987ms2026-10-20 UTC: p95 338ms2026-10-21 UTC: p95 672ms2026-10-22 UTC: p95 350ms2026-10-23 UTC: p95 341ms2026-10-24 UTC: p95 452ms2026-10-25 UTC: p95 473ms2026-10-26 UTC: p95 414ms2026-10-27 UTC: p95 472ms2026-10-28 UTC: p95 319ms2026-10-29 UTC: p95 377ms2026-10-30 UTC: p95 321ms2026-10-31 UTC: p95 290ms2026-11-01 UTC: p95 824ms2026-11-02 UTC: p95 858ms2026-11-03 UTC: p95 93ms2026-11-04 UTC: p95 463ms2026-11-05 UTC: p95 295ms
Oct 7Oct 21Nov 5
Southeast Asia
1.7sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 948ms2026-10-08 UTC: p95 953ms2026-10-09 UTC: p95 1.0s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 612ms2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 614ms2026-10-15 UTC: p95 755ms2026-10-16 UTC: p95 668ms2026-10-17 UTC: p95 767ms2026-10-18 UTC: p95 641ms2026-10-19 UTC: p95 711ms2026-10-20 UTC: p95 630ms2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 702ms2026-10-23 UTC: p95 734ms2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.8s2026-10-28 UTC: p95 1.1s2026-10-29 UTC: p95 1.8s2026-10-30 UTC: p95 1.8s2026-10-31 UTC: p95 2.0s2026-11-01 UTC: p95 2.5s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.7s
Oct 7Oct 21Nov 5
Australia
1.1sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 972ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 959ms2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.0s2026-10-14 UTC: p95 698ms2026-10-15 UTC: p95 695ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 922ms2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 771ms2026-10-25 UTC: p95 684ms2026-10-26 UTC: p95 856ms2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 809ms2026-10-29 UTC: p95 2.9s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 786ms2026-11-01 UTC: p95 652ms2026-11-02 UTC: p95 992ms2026-11-03 UTC: p95 1.8s2026-11-04 UTC: p95 2.5s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
South America
2.2sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 780ms2026-10-08 UTC: p95 675ms2026-10-09 UTC: p95 606ms2026-10-10 UTC: p95 682ms2026-10-11 UTC: p95 475ms2026-10-12 UTC: p95 621ms2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 694ms2026-10-15 UTC: p95 640ms2026-10-16 UTC: p95 538ms2026-10-17 UTC: p95 849ms2026-10-18 UTC: p95 878ms2026-10-19 UTC: p95 835ms2026-10-20 UTC: p95 682ms2026-10-21 UTC: p95 675ms2026-10-22 UTC: p95 841ms2026-10-23 UTC: p95 9.5s2026-10-24 UTC: p95 557ms2026-10-25 UTC: p95 503ms2026-10-26 UTC: p95 697ms2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 2.7s2026-10-31 UTC: p95 847ms2026-11-01 UTC: p95 718ms2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 471ms2026-11-04 UTC: p95 941ms2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5

Check your own site while you wait on HashiCorp Cloud

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not HashiCorp Cloud. It cannot diagnose HashiCorp Cloud's own systems.

Email me when HashiCorp Cloud reports an incident on its status page, and again when it reports it resolved.

Get an email when HashiCorp Cloud reports an incident

Email me when HashiCorp Cloud reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is HashiCorp Cloud's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1052msstatus code: 200checked: Nov 5, 2026, 2:25 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach HashiCorp Cloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 846msstatus code: 200checked: Nov 5, 2026, 1:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach HashiCorp Cloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 68msstatus code: 200checked: Nov 5, 2026, 2:22 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach HashiCorp Cloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 366msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach HashiCorp Cloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 217msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach HashiCorp Cloud normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 191msstatus code: 200checked: Nov 5, 2026, 2:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach HashiCorp Cloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 90msstatus code: 200checked: Nov 5, 2026, 2:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach HashiCorp Cloud normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1576msstatus code: 200checked: Nov 5, 2026, 2:26 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach HashiCorp Cloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 327msstatus code: 200checked: Nov 5, 2026, 2:20 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach HashiCorp Cloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 372msstatus code: 200checked: Nov 5, 2026, 2:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach HashiCorp Cloud normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using HashiCorp Cloud, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for HashiCorp Cloud yet, which is not evidence that nothing is wrong.

Recent probe events

HCP Terraform – Elevated 502 Bad Gateway Errors, 1h 51mdeclared on their status page2026-11-05
GitHub and Other VCS workloads experiencing intermittent issues, 2h 45mdeclared on their status page2026-10-22
HCP Terraform Scheduled Maintenance (2026-11-14)declared on their status page2026-10-15
Terraform Runs Failing, 22mdeclared on their status page2026-10-13
HCP Vault Azure: Cluster Updates and Creation, 126h 5mdeclared on their status page2026-10-04
Users unable to access releases.hashicorp.con, 57mdeclared on their status page2026-09-26
HCP Terraform Returning 404s, 2h 19mdeclared on their status page2026-09-23
Degraded commit/content scans in HCP Vault Radar, 4h 40mdeclared on their status page2026-09-16

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring HashiCorp Cloud since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for HashiCorp Cloud covering any window you pick, with our check readings and HashiCorp Cloud's own claim at the time, side by side.

Full check history for HashiCorp Cloud: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

HashiCorp Cloud uptime by RealUptime's checksLive, from this page's own readings.
[![HashiCorp Cloud uptime by RealUptime's checks](https://realuptime.io/outages/hashicorp/badge.svg?days=30)](https://realuptime.io/outages/hashicorp)
<a href="https://realuptime.io/outages/hashicorp"><img src="https://realuptime.io/outages/hashicorp/badge.svg?days=30" alt="HashiCorp Cloud uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is HashiCorp Cloud down?", https://realuptime.io/outages/hashicorp. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://registry.terraform.io/.well-known/terraform.json
secondary
https://status.hashicorp.com/

What our check can and cannot see

A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.

Host checked: registry.terraform.io

RealUptime is not affiliated with HashiCorp Cloud; the name identifies what we checked, and nothing here speaks for HashiCorp Cloud's own team. We send a single web request to HashiCorp Cloud from 10 regions on our own schedule and time the response. We do not see inside HashiCorp Cloud's systems, do not use an account or real transaction, and are not the same signal HashiCorp Cloud's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for HashiCorp Cloud is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.