User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 59 min ago. Last stored result reached it in 80 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 65 ms | 0 |
| Tue 02 | 0 | 0.0 | 33 ms | 0 |
| Tue 04 | 0 | 0.0 | 45 ms | 0 |
| Tue 06 | 0 | 0.0 | 68 ms | 0 |
| Tue 09 | 0 | 0.0 | 40 ms | 0 |
| Tue 11 | 0 | 0.0 | 140 ms | 0 |
| Tue 13 | 0 | 0.0 | 148 ms | 0 |
| Tue 15 | 0 | 0.0 | 117 ms | 0 |
| Tue 17 | 0 | 0.0 | 73 ms | 0 |
| Tue 20 | 0 | 0.0 | 364 ms | 0 |
| Tue 22 | 0 | 0.0 | 71 ms | 0 |
| Wed 00 | 0 | 0.0 | 68 ms | 0 |
| Wed 02 | 0 | 0.0 | 38 ms | 0 |
| Wed 05 | 0 | 0.0 | 55 ms | 0 |
| Wed 07 | 0 | 0.0 | 381 ms | 0 |
| Wed 09 | 0 | 0.0 | 50 ms | 0 |
| Wed 11 | 0 | 0.0 | 278 ms | 0 |
| Wed 13 | 0 | 0.0 | 155 ms | 0 |
| Wed 15 | 0 | 0.0 | 29 ms | 0 |
| Wed 18 | 0 | 0.0 | 113 ms | 0 |
| Wed 20 | 0 | 0.0 | 165 ms | 0 |
| Wed 22 | 0 | 0.0 | 42 ms | 0 |
| Thu 00 | 0 | 0.0 | 168 ms | 0 |
| Thu 02 | 0 | 0.0 | 192 ms | 0 |
| Thu 04 | 0 | 0.0 | 177 ms | 0 |
| Thu 06 | 0 | 0.0 | 242 ms | 0 |
| Thu 08 | 0 | 0.0 | 71 ms | 0 |
| Thu 11 | 0 | 0.0 | 204 ms | 0 |
| Thu 13 | 0 | 0.0 | 51 ms | 0 |
| Thu 15 | 0 | 0.0 | 224 ms | 0 |
| Thu 17 | 0 | 0.0 | 104 ms | 0 |
| Thu 19 | 0 | 0.0 | 66 ms | 0 |
| Thu 20 | 0 | 0.0 | 114 ms | 0 |
| Thu 22 | 0 | 0.0 | 44 ms | 0 |
| Fri 00 | 0 | 0.0 | 44 ms | 0 |
| Fri 02 | 0 | 0.0 | 54 ms | 0 |
| Fri 04 | 0 | 0.0 | 135 ms | 0 |
| Fri 06 | 0 | 0.0 | 638 ms | 0 |
| Fri 07 | 0 | 0.0 | 64 ms | 0 |
| Fri 09 | 0 | 0.0 | 43 ms | 0 |
| Fri 10 | 0 | 0.0 | 55 ms | 0 |
| Fri 12 | 0 | 0.0 | 93 ms | 0 |
| Fri 14 | 0 | 0.0 | 66 ms | 0 |
| Fri 16 | 0 | 0.0 | 185 ms | 0 |
| Fri 17 | 0 | 0.0 | 104 ms | 0 |
| Fri 19 | 0 | 0.0 | 49 ms | 0 |
| Fri 21 | 0 | 0.0 | 180 ms | 0 |
| Fri 23 | 0 | 0.0 | 80 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for GoFormz 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 GoFormz goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GoFormz alerts to Slack, Discord or a webhook — free.
We track GoFormz (goformz.com) as part of the Productivity group. Use the GoFormz mobile forms and data capture platform to fill out forms on mobile devices and computers, even offline. Your mobile forms can look exactly like your existing paper forms, and be used to collect images, gps, signatures and more. Sign up for a free account!
GoFormz publishes an official status page at status.goformz.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 120 ms average, 30–638 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 GoFormz incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
120 ms on average over the last 24 hours (30–638 ms).
Yes, at https://status.goformz.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report GoFormz here at once, the problem is on GoFormz'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 GoFormz. 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.