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 2 hr ago. Last stored result reached it in 263 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 265 ms | 0 |
| Mon 22 | 0 | 0.0 | 181 ms | 0 |
| Tue 00 | 0 | 0.0 | 252 ms | 0 |
| Tue 02 | 0 | 0.0 | 231 ms | 0 |
| Tue 04 | 0 | 0.0 | 261 ms | 0 |
| Tue 06 | 0 | 0.0 | 180 ms | 0 |
| Tue 08 | 0 | 0.0 | 193 ms | 0 |
| Tue 10 | 0 | 0.0 | 230 ms | 0 |
| Tue 13 | 0 | 0.0 | 68 ms | 0 |
| Tue 15 | 0 | 0.0 | 223 ms | 0 |
| Tue 17 | 0 | 0.0 | 217 ms | 0 |
| Tue 19 | 0 | 0.0 | 255 ms | 0 |
| Tue 22 | 0 | 0.0 | 154 ms | 0 |
| Wed 00 | 0 | 0.0 | 66 ms | 0 |
| Wed 02 | 0 | 0.0 | 177 ms | 0 |
| Wed 04 | 0 | 0.0 | 225 ms | 0 |
| Wed 07 | 0 | 0.0 | 229 ms | 0 |
| Wed 09 | 0 | 0.0 | 198 ms | 0 |
| Wed 11 | 0 | 0.0 | 244 ms | 0 |
| Wed 13 | 0 | 0.0 | 185 ms | 0 |
| Wed 15 | 0 | 0.0 | 291 ms | 0 |
| Wed 17 | 0 | 0.0 | 286 ms | 0 |
| Wed 20 | 0 | 0.0 | 243 ms | 0 |
| Wed 22 | 0 | 0.0 | 206 ms | 0 |
| Thu 00 | 0 | 0.0 | 321 ms | 0 |
| Thu 02 | 0 | 0.0 | 189 ms | 0 |
| Thu 04 | 0 | 0.0 | 286 ms | 0 |
| Thu 06 | 0 | 0.0 | 286 ms | 0 |
| Thu 08 | 0 | 0.0 | 269 ms | 0 |
| Thu 10 | 0 | 0.0 | 190 ms | 0 |
| Thu 12 | 0 | 0.0 | 217 ms | 0 |
| Thu 15 | 0 | 0.0 | 59 ms | 0 |
| Thu 17 | 0 | 0.0 | 260 ms | 0 |
| Thu 19 | 0 | 0.0 | 573 ms | 0 |
| Thu 21 | 0 | 0.0 | 126 ms | 0 |
| Thu 23 | 0 | 0.0 | 200 ms | 0 |
| Fri 01 | 0 | 0.0 | 245 ms | 0 |
| Fri 03 | 0 | 0.0 | 178 ms | 0 |
| Fri 05 | 0 | 0.0 | 260 ms | 0 |
| Fri 07 | 0 | 0.0 | 191 ms | 0 |
| Fri 09 | 0 | 0.0 | 247 ms | 0 |
| Fri 10 | 0 | 0.0 | 179 ms | 0 |
| Fri 12 | 0 | 0.0 | 190 ms | 0 |
| Fri 14 | 0 | 0.0 | 196 ms | 0 |
| Fri 16 | 0 | 0.0 | 247 ms | 0 |
| Fri 18 | 0 | 0.0 | 261 ms | 0 |
| Fri 20 | 0 | 0.0 | 293 ms | 0 |
| Fri 22 | 0 | 0.0 | 263 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 Stormboard 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 Stormboard goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Stormboard alerts to Slack, Discord or a webhook — free.
We track Stormboard (stormboard.com) as part of the Productivity group. Stormboard is the data-first collaborative workflow platform that turns unstructured interactions into data-rich collaborative workspaces, creating new structured and actionable data from normal human collaboration, whether in-person or across distance.
Stormboard publishes an official status page at status.stormboard.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: 230 ms average, 166–296 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Stormboard incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
230 ms on average over the last 24 hours (166–296 ms).
Yes, at https://status.stormboard.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 Stormboard here at once, the problem is on Stormboard'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 Stormboard. 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.