User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
workflowy.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 278 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 05:00 | 0 | 0.0 | 366 ms | 0 |
| 05:15 | 0 | 0.0 | 763 ms | 0 |
| 05:30 | 0 | 0.0 | 1067 ms | 0 |
| 05:45 | 0 | 0.0 | 663 ms | 0 |
| 06:00 | 0 | 0.0 | 790 ms | 0 |
| 06:15 | 0 | 0.0 | 556 ms | 0 |
| 06:30 | 0 | 0.0 | 607 ms | 0 |
| 06:45 | 0 | 0.0 | 161 ms | 0 |
| 07:00 | 0 | 0.0 | 1344 ms | 0 |
| 07:15 | 0 | 0.0 | 677 ms | 0 |
| 07:30 | 0 | 0.0 | 1560 ms | 0 |
| 07:45 | 0 | 0.0 | 435 ms | 0 |
| 08:00 | 0 | 0.0 | 1296 ms | 0 |
| 08:15 | 0 | 0.0 | 233 ms | 0 |
| 08:30 | 0 | 0.0 | 290 ms | 0 |
| 08:45 | 0 | 0.0 | 1011 ms | 0 |
| 09:00 | 0 | 0.0 | 705 ms | 0 |
| 09:15 | 0 | 0.0 | 1671 ms | 0 |
| 09:30 | 0 | 0.0 | 953 ms | 0 |
| 09:45 | 0 | 0.0 | 1176 ms | 0 |
| 10:00 | 0 | 0.0 | 575 ms | 0 |
| 10:15 | 0 | 0.0 | 434 ms | 0 |
| 10:30 | 0 | 0.0 | 191 ms | 0 |
| 10:45 | 0 | 0.0 | 362 ms | 0 |
| 11:00 | 0 | 0.0 | 726 ms | 0 |
| 11:15 | 0 | 0.0 | 1879 ms | 0 |
| 11:30 | 0 | 0.0 | 910 ms | 0 |
| 11:45 | 0 | 0.0 | 1496 ms | 0 |
| 12:00 | 0 | 0.0 | 1088 ms | 0 |
| 12:15 | 0 | 0.0 | 183 ms | 0 |
| 12:30 | 0 | 0.0 | 461 ms | 0 |
| 12:45 | 0 | 0.0 | 977 ms | 0 |
| 13:00 | 0 | 0.0 | 522 ms | 0 |
| 13:15 | 0 | 0.0 | 364 ms | 0 |
| 13:30 | 0 | 0.0 | 297 ms | 0 |
| 13:45 | 0 | 0.0 | 128 ms | 0 |
| 14:00 | 0 | 0.0 | 438 ms | 0 |
| 14:15 | 0 | 0.0 | 196 ms | 0 |
| 14:30 | 0 | 0.0 | 676 ms | 0 |
| 14:45 | 0 | 0.0 | 740 ms | 0 |
| 15:00 | 0 | 0.0 | 1776 ms | 0 |
| 15:15 | 0 | 0.0 | 238 ms | 0 |
| 15:30 | 0 | 0.0 | 1278 ms | 0 |
| 15:45 | 0 | 0.0 | 652 ms | 0 |
| 16:00 | 0 | 0.0 | 1112 ms | 0 |
| 16:15 | 0 | 0.0 | 1154 ms | 0 |
| 16:30 | 0 | 0.0 | 770 ms | 0 |
| 16:45 | 0 | 0.0 | 349 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for WorkFlowy 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 WorkFlowy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WorkFlowy alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If WorkFlowy is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on WorkFlowy's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.