User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
clearstory.build · 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 17 min ago. Last stored result reached it in 106 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 13 | 0 | 0.0 | 70 ms | 0 |
| Tue 15 | 0 | 0.0 | 152 ms | 0 |
| Tue 17 | 0 | 0.0 | 228 ms | 0 |
| Tue 20 | 0 | 0.0 | 95 ms | 0 |
| Tue 22 | 0 | 0.0 | 307 ms | 0 |
| Wed 00 | 0 | 0.0 | 112 ms | 0 |
| Wed 02 | 0 | 0.0 | 104 ms | 0 |
| Wed 05 | 0 | 0.0 | 280 ms | 0 |
| Wed 07 | 0 | 0.0 | 112 ms | 0 |
| Wed 09 | 0 | 0.0 | 238 ms | 0 |
| Wed 11 | 0 | 0.0 | 156 ms | 0 |
| Wed 13 | 0 | 0.0 | 102 ms | 0 |
| Wed 15 | 0 | 0.0 | 188 ms | 0 |
| Wed 18 | 0 | 0.0 | 284 ms | 0 |
| Wed 20 | 0 | 0.0 | 176 ms | 0 |
| Wed 21 | 0 | 0.0 | 152 ms | 0 |
| Thu 00 | 0 | 0.0 | 123 ms | 0 |
| Thu 02 | 0 | 0.0 | 194 ms | 0 |
| Thu 04 | 0 | 0.0 | 97 ms | 0 |
| Thu 05 | 0 | 0.0 | 77 ms | 0 |
| Thu 08 | 0 | 0.0 | 85 ms | 0 |
| Thu 10 | 0 | 0.0 | 178 ms | 0 |
| Thu 12 | 0 | 0.0 | 89 ms | 0 |
| Thu 14 | 0 | 0.0 | 122 ms | 0 |
| Thu 16 | 0 | 0.0 | 83 ms | 0 |
| Thu 18 | 0 | 0.0 | 240 ms | 0 |
| Thu 20 | 0 | 0.0 | 151 ms | 0 |
| Thu 22 | 0 | 0.0 | 163 ms | 0 |
| Fri 00 | 0 | 0.0 | 324 ms | 0 |
| Fri 02 | 0 | 0.0 | 74 ms | 0 |
| Fri 04 | 0 | 0.0 | 298 ms | 0 |
| Fri 07 | 0 | 0.0 | 220 ms | 0 |
| Fri 09 | 0 | 0.0 | 62 ms | 0 |
| Fri 11 | 0 | 0.0 | 105 ms | 0 |
| Fri 13 | 0 | 0.0 | 153 ms | 0 |
| Fri 15 | 0 | 0.0 | 135 ms | 0 |
| Fri 17 | 0 | 0.0 | 204 ms | 0 |
| Fri 19 | 0 | 0.0 | 296 ms | 0 |
| Fri 21 | 0 | 0.0 | 219 ms | 0 |
| Fri 22 | 0 | 0.0 | 100 ms | 0 |
| Sat 00 | 0 | 0.0 | 54 ms | 0 |
| Sat 02 | 0 | 0.0 | 140 ms | 0 |
| Sat 04 | 0 | 0.0 | 131 ms | 0 |
| Sat 05 | 0 | 0.0 | 97 ms | 0 |
| Sat 07 | 0 | 0.0 | 134 ms | 0 |
| Sat 10 | 0 | 0.0 | 99 ms | 0 |
| Sat 12 | 0 | 0.0 | 106 ms | 0 |
| Sat 13 | 0 | 0.0 | 132 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Clearstory 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 Clearstory goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Clearstory alerts to Slack, Discord or a webhook — free.
Clearstory is listed in our Productivity category and checked at clearstory.build. Streamline project communication with real-time Change Orders and T&M Tags. Reduce risk, save time, and increase transparency for GCs, Specialty Contractors, and Owners.
Clearstory publishes an official status page at status.clearstory.build; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 146 ms average, 54–296 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Clearstory incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
146 ms on average over the last 24 hours (54–296 ms).
Yes, at https://status.clearstory.build.
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 Clearstory here at once, the problem is on Clearstory'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 Clearstory. 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.