← Back to HashiCorp Cloud's check readings
We started checking HashiCorp Cloud on August 20, 2026, which is 66 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when HashiCorp Cloud reports an incident on its status page, and again when it reports it resolved.
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what HashiCorp Cloud's own status page declared. Below it, any public chatter we saw about HashiCorp Cloud and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what HashiCorp Cloud's own status page declared. Three records side by side; none of them changes another.
- GitHub and Other VCS workloads experiencing intermittent issues: partial outage, from 17:15 UTC to 20:15 UTC.
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is HashiCorp Cloud's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention HashiCorp Cloud next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
- Confirmation probe17:35 UTC, Southeast Asia: their own status feed changing prompted an extra probe. Result: HashiCorp Cloud answered normally.
- Confirmation probe17:35 UTC, US-Central: their own status feed changing prompted an extra probe. Result: HashiCorp Cloud answered normally.
- Confirmation probe17:34 UTC, US-West: their own status feed changing prompted an extra probe. Result: HashiCorp Cloud answered normally.
- Confirmation probe17:34 UTC, Canada: their own status feed changing prompted an extra probe. Result: HashiCorp Cloud answered normally.
- Confirmation probe17:34 UTC, US-East: their own status feed changing prompted an extra probe. Result: HashiCorp Cloud answered normally.
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
| Region | Checks passing | Probes recorded |
|---|---|---|
| US-East | 99.97% | 3070 |
| US-West | 100.00% | 3069 |
| Europe | 99.97% | 3066 |
| Asia-Pacific | 100.00% | 3042 |
| US-Central | 100.00% | 1233 |
| Canada | 99.92% | 1233 |
| UK | 100.00% | 1233 |
| Southeast Asia | 100.00% | 1229 |
| Australia | 99.84% | 1228 |
| South America | 99.51% | 1231 |
Their declared record
HashiCorp Cloud's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Showing the 10 most recent of 34 incidents HashiCorp Cloud has declared in the history we hold.
These entries are HashiCorp Cloud's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
HashiCorp Cloud's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.