Skip to content

Outage tracker / HashiCorp Cloud

Is HashiCorp Cloud down?

I'm having a problem

Operationalchecked 1 minute ago

We reached HashiCorp Cloud from all 10 regions we check.

As of Oct 5, 2026, 8:16 PM UTC, HashiCorp Cloud answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 46 days we have measured HashiCorp Cloud (since Aug 20, 2026).

HashiCorp Cloud reports an active incident: "HCP Vault Azure: Cluster Updates and Creation" (all systems operational, since Oct 4, 2026, 12:38 AM UTC). That is their claim, not our measurement: our probes are currently reaching HashiCorp Cloud, and an incident they declare can affect parts of the service our checks do not exercise. We show both and never merge them.

our independent probeslive · checked Oct 5, 2026, 8:16 PM UTC
US-East296 msOperational
US-West428 msOperational
Europe554 msOperational
Asia-Pacific598 msOperational
US-Central253 msOperational
Canada361 msOperational
UK255 msOperational
Southeast Asia357 msOperational
Australia1102 msOperational
South America529 msOperational
their status pagetheir claim, not our reading

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

from HashiCorp Cloud's own status page, checked Oct 5, 2026, 7:58 PM UTC

HashiCorp Cloud reports an active incident: HCP Vault Azure: Cluster Updates and Creation (all systems operational, since Oct 4, 2026, 12:38 AM UTC). Their summary currently reads “All systems operational” even so: the summary and the incident come from two separately polled feeds and can disagree.

Our probes and HashiCorp Cloud's own status page agree: both show HashiCorp Cloud as reachable 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
386msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 410ms2026-09-07 UTC: p95 400ms2026-09-08 UTC: p95 420ms2026-09-09 UTC: p95 426ms2026-09-10 UTC: p95 425ms2026-09-11 UTC: p95 513ms2026-09-12 UTC: p95 462ms2026-09-13 UTC: p95 475ms2026-09-14 UTC: p95 416ms2026-09-15 UTC: p95 398ms2026-09-16 UTC: p95 546ms2026-09-17 UTC: p95 647ms2026-09-18 UTC: p95 385ms2026-09-19 UTC: p95 397ms2026-09-20 UTC: p95 441ms2026-09-21 UTC: p95 377ms2026-09-22 UTC: p95 494ms2026-09-23 UTC: p95 522ms2026-09-24 UTC: p95 415ms2026-09-25 UTC: p95 384ms2026-09-26 UTC: p95 404ms2026-09-27 UTC: p95 404ms2026-09-28 UTC: p95 413ms2026-09-29 UTC: p95 392ms2026-09-30 UTC: p95 394ms2026-10-01 UTC: p95 605ms2026-10-02 UTC: p95 405ms2026-10-03 UTC: p95 383ms2026-10-04 UTC: p95 565ms2026-10-05 UTC: p95 386ms
Sep 6Sep 20Oct 5
US-West
730msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 786ms2026-09-07 UTC: p95 754ms2026-09-08 UTC: p95 874ms2026-09-09 UTC: p95 730ms2026-09-10 UTC: p95 635ms2026-09-11 UTC: p95 410ms2026-09-12 UTC: p95 557ms2026-09-13 UTC: p95 399ms2026-09-14 UTC: p95 522ms2026-09-15 UTC: p95 492ms2026-09-16 UTC: p95 455ms2026-09-17 UTC: p95 481ms2026-09-18 UTC: p95 575ms2026-09-19 UTC: p95 465ms2026-09-20 UTC: p95 526ms2026-09-21 UTC: p95 545ms2026-09-22 UTC: p95 741ms2026-09-23 UTC: p95 618ms2026-09-24 UTC: p95 582ms2026-09-25 UTC: p95 536ms2026-09-26 UTC: p95 612ms2026-09-27 UTC: p95 498ms2026-09-28 UTC: p95 538ms2026-09-29 UTC: p95 439ms2026-09-30 UTC: p95 580ms2026-10-01 UTC: p95 476ms2026-10-02 UTC: p95 656ms2026-10-03 UTC: p95 497ms2026-10-04 UTC: p95 787ms2026-10-05 UTC: p95 730ms
Sep 6Sep 20Oct 5
Europe
602msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 662ms2026-09-07 UTC: p95 672ms2026-09-08 UTC: p95 676ms2026-09-09 UTC: p95 684ms2026-09-10 UTC: p95 588ms2026-09-11 UTC: p95 438ms2026-09-12 UTC: p95 404ms2026-09-13 UTC: p95 614ms2026-09-14 UTC: p95 708ms2026-09-15 UTC: p95 729ms2026-09-16 UTC: p95 681ms2026-09-17 UTC: p95 419ms2026-09-18 UTC: p95 435ms2026-09-19 UTC: p95 405ms2026-09-20 UTC: p95 394ms2026-09-21 UTC: p95 391ms2026-09-22 UTC: p95 507ms2026-09-23 UTC: p95 521ms2026-09-24 UTC: p95 594ms2026-09-25 UTC: p95 615ms2026-09-26 UTC: p95 465ms2026-09-27 UTC: p95 426ms2026-09-28 UTC: p95 399ms2026-09-29 UTC: p95 386ms2026-09-30 UTC: p95 549ms2026-10-01 UTC: p95 578ms2026-10-02 UTC: p95 586ms2026-10-03 UTC: p95 674ms2026-10-04 UTC: p95 863ms2026-10-05 UTC: p95 602ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.0sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 850ms2026-09-07 UTC: p95 814ms2026-09-08 UTC: p95 1.0s2026-09-09 UTC: p95 951ms2026-09-10 UTC: p95 907ms2026-09-11 UTC: p95 743ms2026-09-12 UTC: p95 792ms2026-09-13 UTC: p95 955ms2026-09-14 UTC: p95 974ms2026-09-15 UTC: p95 943ms2026-09-16 UTC: p95 934ms2026-09-17 UTC: p95 585ms2026-09-18 UTC: p95 678ms2026-09-19 UTC: p95 632ms2026-09-20 UTC: p95 627ms2026-09-21 UTC: p95 582ms2026-09-22 UTC: p95 684ms2026-09-23 UTC: p95 749ms2026-09-24 UTC: p95 994ms2026-09-25 UTC: p95 884ms2026-09-26 UTC: p95 795ms2026-09-27 UTC: p95 842ms2026-09-28 UTC: p95 696ms2026-09-29 UTC: p95 652ms2026-09-30 UTC: p95 941ms2026-10-01 UTC: p95 658ms2026-10-02 UTC: p95 1.0s2026-10-03 UTC: p95 925ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.0s
Sep 6Sep 20Oct 5
US-Central
347msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 482ms2026-09-07 UTC: p95 577ms2026-09-08 UTC: p95 678ms2026-09-09 UTC: p95 566ms2026-09-10 UTC: p95 480ms2026-09-11 UTC: p95 616ms2026-09-12 UTC: p95 579ms2026-09-13 UTC: p95 442ms2026-09-14 UTC: p95 751ms2026-09-15 UTC: p95 446ms2026-09-16 UTC: p95 451ms2026-09-17 UTC: p95 537ms2026-09-18 UTC: p95 734ms2026-09-19 UTC: p95 488ms2026-09-20 UTC: p95 527ms2026-09-21 UTC: p95 382ms2026-09-22 UTC: p95 593ms2026-09-23 UTC: p95 489ms2026-09-24 UTC: p95 575ms2026-09-25 UTC: p95 444ms2026-09-26 UTC: p95 521ms2026-09-27 UTC: p95 405ms2026-09-28 UTC: p95 487ms2026-09-29 UTC: p95 545ms2026-09-30 UTC: p95 490ms2026-10-01 UTC: p95 473ms2026-10-02 UTC: p95 501ms2026-10-03 UTC: p95 505ms2026-10-04 UTC: p95 423ms2026-10-05 UTC: p95 347ms
Sep 6Sep 20Oct 5
Canada
571msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 535ms2026-09-07 UTC: p95 650ms2026-09-08 UTC: p95 639ms2026-09-09 UTC: p95 732ms2026-09-10 UTC: p95 490ms2026-09-11 UTC: p95 564ms2026-09-12 UTC: p95 511ms2026-09-13 UTC: p95 570ms2026-09-14 UTC: p95 480ms2026-09-15 UTC: p95 478ms2026-09-16 UTC: p95 476ms2026-09-17 UTC: p95 518ms2026-09-18 UTC: p95 531ms2026-09-19 UTC: p95 542ms2026-09-20 UTC: p95 492ms2026-09-21 UTC: p95 466ms2026-09-22 UTC: p95 501ms2026-09-23 UTC: p95 490ms2026-09-24 UTC: p95 561ms2026-09-25 UTC: p95 513ms2026-09-26 UTC: p95 467ms2026-09-27 UTC: p95 477ms2026-09-28 UTC: p95 451ms2026-09-29 UTC: p95 585ms2026-09-30 UTC: p95 566ms2026-10-01 UTC: p95 518ms2026-10-02 UTC: p95 483ms2026-10-03 UTC: p95 481ms2026-10-04 UTC: p95 500ms2026-10-05 UTC: p95 571ms
Sep 6Sep 20Oct 5
UK
317msp95 · 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-09-06 UTC: p95 283ms2026-09-07 UTC: p95 382ms2026-09-08 UTC: p95 272ms2026-09-09 UTC: p95 492ms2026-09-10 UTC: p95 258ms2026-09-11 UTC: p95 315ms2026-09-12 UTC: p95 457ms2026-09-13 UTC: p95 363ms2026-09-14 UTC: p95 270ms2026-09-15 UTC: p95 290ms2026-09-16 UTC: p95 326ms2026-09-17 UTC: p95 263ms2026-09-18 UTC: p95 291ms2026-09-19 UTC: p95 261ms2026-09-20 UTC: p95 270ms2026-09-21 UTC: p95 648ms2026-09-22 UTC: p95 434ms2026-09-23 UTC: p95 303ms2026-09-24 UTC: p95 343ms2026-09-25 UTC: p95 301ms2026-09-26 UTC: p95 336ms2026-09-27 UTC: p95 284ms2026-09-28 UTC: p95 338ms2026-09-29 UTC: p95 333ms2026-09-30 UTC: p95 427ms2026-10-01 UTC: p95 480ms2026-10-02 UTC: p95 458ms2026-10-03 UTC: p95 528ms2026-10-04 UTC: p95 289ms2026-10-05 UTC: p95 317ms
Sep 6Sep 20Oct 5
Southeast Asia
665msp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 771ms2026-09-07 UTC: p95 726ms2026-09-08 UTC: p95 707ms2026-09-09 UTC: p95 799ms2026-09-10 UTC: p95 684ms2026-09-11 UTC: p95 598ms2026-09-12 UTC: p95 582ms2026-09-13 UTC: p95 678ms2026-09-14 UTC: p95 605ms2026-09-15 UTC: p95 668ms2026-09-16 UTC: p95 618ms2026-09-17 UTC: p95 656ms2026-09-18 UTC: p95 898ms2026-09-19 UTC: p95 767ms2026-09-20 UTC: p95 609ms2026-09-21 UTC: p95 935ms2026-09-22 UTC: p95 812ms2026-09-23 UTC: p95 997ms2026-09-24 UTC: p95 1.0s2026-09-25 UTC: p95 813ms2026-09-26 UTC: p95 1.1s2026-09-27 UTC: p95 785ms2026-09-28 UTC: p95 859ms2026-09-29 UTC: p95 743ms2026-09-30 UTC: p95 709ms2026-10-01 UTC: p95 748ms2026-10-02 UTC: p95 692ms2026-10-03 UTC: p95 722ms2026-10-04 UTC: p95 659ms2026-10-05 UTC: p95 665ms
Sep 6Sep 20Oct 5
Australia
1.4sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 939ms2026-09-07 UTC: p95 925ms2026-09-08 UTC: p95 949ms2026-09-09 UTC: p95 826ms2026-09-10 UTC: p95 799ms2026-09-11 UTC: p95 698ms2026-09-12 UTC: p95 890ms2026-09-13 UTC: p95 703ms2026-09-14 UTC: p95 811ms2026-09-15 UTC: p95 754ms2026-09-16 UTC: p95 852ms2026-09-17 UTC: p95 729ms2026-09-18 UTC: p95 606ms2026-09-19 UTC: p95 883ms2026-09-20 UTC: p95 878ms2026-09-21 UTC: p95 722ms2026-09-22 UTC: p95 765ms2026-09-23 UTC: p95 757ms2026-09-24 UTC: p95 809ms2026-09-25 UTC: p95 887ms2026-09-26 UTC: p95 921ms2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
South America
716msp95 · latest
1s500ms0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 683ms2026-09-07 UTC: p95 665ms2026-09-08 UTC: p95 989ms2026-09-09 UTC: p95 673ms2026-09-10 UTC: p95 475ms2026-09-11 UTC: p95 571ms2026-09-12 UTC: p95 553ms2026-09-13 UTC: p95 555ms2026-09-14 UTC: p95 507ms2026-09-15 UTC: p95 648ms2026-09-16 UTC: p95 478ms2026-09-17 UTC: p95 655ms2026-09-18 UTC: p95 635ms2026-09-19 UTC: p95 676ms2026-09-20 UTC: p95 571ms2026-09-21 UTC: p95 498ms2026-09-22 UTC: p95 644ms2026-09-23 UTC: p95 683ms2026-09-24 UTC: p95 883ms2026-09-25 UTC: p95 576ms2026-09-26 UTC: p95 791ms2026-09-27 UTC: p95 504ms2026-09-28 UTC: p95 507ms2026-09-29 UTC: p95 783ms2026-09-30 UTC: p95 758ms2026-10-01 UTC: p95 851ms2026-10-02 UTC: p95 973ms2026-10-03 UTC: p95 775ms2026-10-04 UTC: p95 971ms2026-10-05 UTC: p95 716ms
Sep 6Sep 20Oct 5

Is it HashiCorp Cloud, or is it you?

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.

Get an email when we see HashiCorp Cloud go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching HashiCorp Cloud, and again when they can reach it again. That is our own measurement from ten regions, not HashiCorp Cloud's status page. No account, no card.

Delivery channel

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

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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 296msstatus code: 200checked: Oct 5, 2026, 7:53 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
      Operationallatency: 428msstatus code: 200checked: Oct 5, 2026, 7:47 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
      Operationallatency: 253msstatus code: 200checked: Oct 5, 2026, 7:38 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
      Operationallatency: 361msstatus code: 200checked: Oct 5, 2026, 7:45 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
    Operationallatency: 529msstatus code: 200checked: Oct 5, 2026, 7:40 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 554msstatus code: 200checked: Oct 5, 2026, 7:51 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
      Operationallatency: 255msstatus code: 200checked: Oct 5, 2026, 7:40 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 598msstatus code: 200checked: Oct 5, 2026, 8:16 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
      Operationallatency: 357msstatus code: 200checked: Oct 5, 2026, 7:47 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
      Operationallatency: 1102msstatus code: 200checked: Oct 5, 2026, 7:54 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 outages

HCP Vault Azure: Cluster Updates and Creationdeclared 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
Hashicorp Linux packages GPG key rotation, 7h 17mdeclared on their status page2026-09-10
Errors creating new VCS workspaces with Bitbucket cloud provider, 3h 54mdeclared on their status page2026-09-04
Delayed HCP Terraform Runs, 67h 42mdeclared on their status page2026-08-15
Terraform AWS Provider v6.59.0 — errors during plan for aws_network_acl_rule resources, 1h 16mdeclared on their status page2026-08-13

measured 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 measurements and HashiCorp Cloud's own claim at the time, side by side.

Full availability history for HashiCorp Cloud: 90-day availability by region, month-by-month uptime, and every incident 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

Put this badge in your README

HashiCorp Cloud uptime measured by RealUptimeLive, from this page's own readings.
[![HashiCorp Cloud uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What HashiCorp Cloud's SLA implies, from our measurement

At or above your target

We measured none of downtime for HashiCorp Cloud over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from HashiCorp Cloud's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://registry.terraform.io/v1/providers/hashicorp/aws
secondary
https://status.hashicorp.com/
RealUptime is not affiliated with HashiCorp Cloud; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.