We started checking Terraform Registry on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Terraform Registry reports an incident on its status page, and again when it reports it resolved.
01
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 Terraform Registry's own status page declared. Below it, any public chatter we saw about Terraform Registry 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 Terraform Registry's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Terraform Registry in the last 24 hours, which is not evidence that nothing is wrong.
Terraform Registry's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
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 Terraform Registry's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Terraform Registry 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.
02
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
100.00%
3087
US-West
99.91%
2230
Europe
100.00%
2077
Asia-Pacific
100.00%
1269
Their declared record
Terraform Registry's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
HCP Boundary Scheduled MaintenancePartial outage
Nov 6, 2026, 3:09 PM UTC to Nov 6, 2026, 3:15 PM UTC (7 min)resolved
their latest update (Nov 6, 2026, 3:15 PM UTC): This is intended for Nov 14, so resolving at this moment.
HCP Terraform – Elevated 502 Bad Gateway ErrorsMinor incident
Nov 5, 2026, 8:13 AM UTC to Nov 5, 2026, 10:04 AM UTC (1h 51m)resolved
their latest update (Nov 5, 2026, 10:04 AM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
GitHub and Other VCS workloads experiencing intermittent issuesPartial outage
Oct 22, 2026, 5:15 PM UTC to Oct 22, 2026, 8:01 PM UTC (2h 45m)resolved
their latest update (Oct 23, 2026, 9:07 PM UTC): Today we released tfc-agent 1.33.3 to address the root cause of the failures we saw yesterday. A recent security patch to libcurl exposed a bug in the version of git we ship in the tfc-agent image. This causes some VCS setups to fail when the VCS provider issues an HTTP redirect.…
Terraform Runs FailingPartial outage
Oct 13, 2026, 4:01 PM UTC to Oct 13, 2026, 4:23 PM UTC (22 min)resolved
their latest update (Oct 13, 2026, 4:23 PM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
HCP Vault Azure: Cluster Updates and CreationAll systems operational
Oct 4, 2026, 12:38 AM UTC to Oct 9, 2026, 6:43 AM UTC (5d 6h)resolved
their latest update (Oct 9, 2026, 6:43 AM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Users unable to access releases.hashicorp.conPartial outage
Sep 26, 2026, 2:06 AM UTC to Sep 26, 2026, 3:03 AM UTC (57 min)resolved
their latest update (Sep 26, 2026, 3:03 AM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
HCP Terraform Returning 404sMajor outage
Sep 23, 2026, 5:43 PM UTC to Sep 23, 2026, 8:02 PM UTC (2h 19m)resolved
their latest update (Sep 23, 2026, 8:02 PM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Degraded commit/content scans in HCP Vault RadarMinor incident
Sep 16, 2026, 5:41 PM UTC to Sep 16, 2026, 10:21 PM UTC (4h 40m)resolved
their latest update (Sep 16, 2026, 10:21 PM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Hashicorp Linux packages GPG key rotationPartial outage
Sep 10, 2026, 1:24 PM UTC to Sep 10, 2026, 8:40 PM UTC (7h 17m)resolved
their latest update (Sep 10, 2026, 8:40 PM UTC): Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Errors creating new VCS workspaces with Bitbucket cloud providerMinor incident
Sep 4, 2026, 5:51 PM UTC to Sep 4, 2026, 9:46 PM UTC (3h 54m)resolved
their latest update (Sep 4, 2026, 9:46 PM UTC): Our Engineering team has resolved the issue with creating new VCS workspaces with the Bitbucket cloud provider. If you continue to experience any problems, please open a ticket with our support team.
Showing the 10 most recent of 27 incidents Terraform Registry has declared in the history we hold.
These entries are Terraform Registry'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.
Terraform Registry'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.