User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
opentofu.org · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 29 min ago. Last stored result reached it in 115 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 88 ms | 0 |
| Tue 08 | 0 | 0.0 | 68 ms | 0 |
| Tue 10 | 0 | 0.0 | 79 ms | 0 |
| Tue 12 | 0 | 0.0 | 68 ms | 0 |
| Tue 14 | 0 | 0.0 | 261 ms | 0 |
| Tue 16 | 0 | 0.0 | 120 ms | 0 |
| Tue 19 | 0 | 0.0 | 105 ms | 0 |
| Tue 21 | 0 | 0.0 | 166 ms | 0 |
| Tue 23 | 0 | 0.0 | 131 ms | 0 |
| Wed 01 | 0 | 0.0 | 89 ms | 0 |
| Wed 04 | 0 | 0.0 | 89 ms | 0 |
| Wed 06 | 0 | 0.0 | 101 ms | 0 |
| Wed 08 | 0 | 0.0 | 97 ms | 0 |
| Wed 10 | 0 | 0.0 | 70 ms | 0 |
| Wed 13 | 0 | 0.0 | 104 ms | 0 |
| Wed 15 | 0 | 0.0 | 79 ms | 0 |
| Wed 17 | 0 | 0.0 | 99 ms | 0 |
| Wed 19 | 0 | 0.0 | 82 ms | 0 |
| Wed 21 | 0 | 0.0 | 141 ms | 0 |
| Wed 23 | 0 | 0.0 | 232 ms | 0 |
| Thu 02 | 0 | 0.0 | 181 ms | 0 |
| Thu 04 | 0 | 0.0 | 158 ms | 0 |
| Thu 06 | 0 | 0.0 | 107 ms | 0 |
| Thu 08 | 0 | 0.0 | 118 ms | 0 |
| Thu 10 | 0 | 0.0 | 80 ms | 0 |
| Thu 12 | 0 | 0.0 | 85 ms | 0 |
| Thu 14 | 0 | 0.0 | 129 ms | 0 |
| Thu 16 | 0 | 0.0 | 93 ms | 0 |
| Thu 18 | 0 | 0.0 | 127 ms | 0 |
| Thu 20 | 0 | 0.0 | 74 ms | 0 |
| Thu 22 | 0 | 0.0 | 111 ms | 0 |
| Fri 00 | 0 | 0.0 | 131 ms | 0 |
| Fri 02 | 0 | 0.0 | 131 ms | 0 |
| Fri 04 | 0 | 0.0 | 141 ms | 0 |
| Fri 06 | 0 | 0.0 | 90 ms | 0 |
| Fri 08 | 0 | 0.0 | 79 ms | 0 |
| Fri 11 | 0 | 0.0 | 97 ms | 0 |
| Fri 13 | 0 | 0.0 | 70 ms | 0 |
| Fri 15 | 0 | 0.0 | 86 ms | 0 |
| Fri 17 | 0 | 0.0 | 162 ms | 0 |
| Fri 18 | 0 | 0.0 | 206 ms | 0 |
| Fri 19 | 0 | 0.0 | 106 ms | 0 |
| Fri 20 | 0 | 0.0 | 171 ms | 0 |
| Fri 22 | 0 | 0.0 | 73 ms | 0 |
| Sat 00 | 0 | 0.0 | 78 ms | 0 |
| Sat 02 | 0 | 0.0 | 82 ms | 0 |
| Sat 04 | 0 | 0.0 | 102 ms | 0 |
| Sat 05 | 0 | 0.0 | 96 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for OpenTofu yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when OpenTofu goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send OpenTofu alerts to Slack, Discord or a webhook — free.
OpenTofu is listed in our Cloud & developer category and checked at opentofu.org. OpenTofu - Modern Infrastructure as Code
OpenTofu publishes an official status page at status.opentofu.org; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 105 ms average, 70–206 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public OpenTofu incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
105 ms on average over the last 24 hours (70–206 ms).
Yes, at https://status.opentofu.org.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report OpenTofu here at once, the problem is on OpenTofu's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with OpenTofu. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.