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 52 min ago. Last stored result reached it in 606 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:45 | 0 | 0.0 | 790 ms | 0 |
| 11:00 | 0 | 0.0 | 825 ms | 0 |
| 13:00 | 0 | 0.0 | 767 ms | 0 |
| 15:00 | 0 | 0.0 | 778 ms | 0 |
| 17:15 | 0 | 0.0 | 649 ms | 0 |
| 19:15 | 0 | 0.0 | 684 ms | 0 |
| 21:15 | 0 | 0.0 | 840 ms | 0 |
| 23:15 | 0 | 0.0 | 782 ms | 0 |
| 01:30 | 0 | 0.0 | 763 ms | 0 |
| 02:30 | 0 | 0.0 | 754 ms | 0 |
| 04:45 | 0 | 0.0 | 723 ms | 0 |
| 06:45 | 0 | 0.0 | 606 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: 748 ms average, 606–840 ms range across 13 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.
748 ms on average over the last 24 hours (606–840 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.