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 6 min ago. Last stored result reached it in 758 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 773 ms | 0 |
| Mon 20 | 0 | 0.0 | 789 ms | 0 |
| Mon 22 | 0 | 0.0 | 844 ms | 0 |
| Tue 00 | 0 | 0.0 | 841 ms | 0 |
| Tue 02 | 0 | 0.0 | 809 ms | 0 |
| Tue 04 | 0 | 0.0 | 817 ms | 0 |
| Tue 06 | 0 | 0.0 | 735 ms | 0 |
| Tue 08 | 0 | 0.0 | 768 ms | 0 |
| Tue 11 | 0 | 0.0 | 702 ms | 0 |
| Tue 13 | 0 | 0.0 | 756 ms | 0 |
| Tue 15 | 0 | 0.0 | 729 ms | 0 |
| Tue 17 | 0 | 0.0 | 1546 ms | 0 |
| Tue 20 | 0 | 0.0 | 743 ms | 0 |
| Tue 22 | 0 | 0.0 | 672 ms | 0 |
| Wed 00 | 0 | 0.0 | 769 ms | 0 |
| Wed 02 | 0 | 0.0 | 749 ms | 0 |
| Wed 05 | 0 | 0.0 | 631 ms | 0 |
| Wed 07 | 0 | 0.0 | 1182 ms | 0 |
| Wed 09 | 0 | 0.0 | 737 ms | 0 |
| Wed 11 | 0 | 0.0 | 603 ms | 0 |
| Wed 13 | 0 | 0.0 | 821 ms | 0 |
| Wed 15 | 0 | 0.0 | 791 ms | 0 |
| Wed 18 | 0 | 0.0 | 749 ms | 0 |
| Wed 20 | 0 | 0.0 | 747 ms | 0 |
| Wed 22 | 0 | 0.0 | 733 ms | 0 |
| Thu 00 | 0 | 0.0 | 835 ms | 0 |
| Thu 02 | 0 | 0.0 | 775 ms | 0 |
| Thu 04 | 0 | 0.0 | 638 ms | 0 |
| Thu 06 | 0 | 0.0 | 751 ms | 0 |
| Thu 08 | 0 | 0.0 | 790 ms | 0 |
| Thu 11 | 0 | 0.0 | 825 ms | 0 |
| Thu 13 | 0 | 0.0 | 767 ms | 0 |
| Thu 15 | 0 | 0.0 | 778 ms | 0 |
| Thu 17 | 0 | 0.0 | 649 ms | 0 |
| Thu 19 | 0 | 0.0 | 684 ms | 0 |
| Thu 21 | 0 | 0.0 | 840 ms | 0 |
| Thu 23 | 0 | 0.0 | 782 ms | 0 |
| Fri 01 | 0 | 0.0 | 763 ms | 0 |
| Fri 02 | 0 | 0.0 | 754 ms | 0 |
| Fri 04 | 0 | 0.0 | 723 ms | 0 |
| Fri 06 | 0 | 0.0 | 606 ms | 0 |
| Fri 08 | 0 | 0.0 | 672 ms | 0 |
| Fri 10 | 0 | 0.0 | 743 ms | 0 |
| Fri 11 | 0 | 0.0 | 792 ms | 0 |
| Fri 13 | 0 | 0.0 | 726 ms | 0 |
| Fri 15 | 0 | 0.0 | 1118 ms | 0 |
| Fri 17 | 0 | 0.0 | 724 ms | 0 |
| Fri 18 | 0 | 0.0 | 738 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 Woopra 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 Woopra goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Woopra alerts to Slack, Discord or a webhook — free.
We track Woopra (woopra.com) as part of the Productivity group. Analyze and visualize the entire customer journey from first marketing touch to product usage. Sign up for our free plan today.
Woopra publishes an official status page at status.woopra.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 760 ms average, 606–1118 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 Woopra incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
760 ms on average over the last 24 hours (606–1118 ms).
Yes, at https://status.woopra.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 Woopra here at once, the problem is on Woopra'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 Woopra. 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.