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 36 min ago. Last stored result reached it in 270 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 05 | 0 | 0.0 | 245 ms | 0 |
| Mon 07 | 0 | 0.0 | 449 ms | 0 |
| Mon 09 | 0 | 0.0 | 270 ms | 0 |
| Mon 11 | 0 | 0.0 | 250 ms | 0 |
| Mon 13 | 0 | 0.0 | 342 ms | 0 |
| Mon 16 | 0 | 0.0 | 242 ms | 0 |
| Mon 18 | 0 | 0.0 | 282 ms | 0 |
| Mon 20 | 0 | 0.0 | 207 ms | 0 |
| Mon 22 | 0 | 0.0 | 266 ms | 0 |
| Tue 00 | 0 | 0.0 | 155 ms | 0 |
| Tue 02 | 0 | 0.0 | 316 ms | 0 |
| Tue 04 | 0 | 0.0 | 338 ms | 0 |
| Tue 06 | 0 | 0.0 | 234 ms | 0 |
| Tue 09 | 0 | 0.0 | 206 ms | 0 |
| Tue 11 | 0 | 0.0 | 262 ms | 0 |
| Tue 13 | 0 | 0.0 | 258 ms | 0 |
| Tue 15 | 0 | 0.0 | 264 ms | 0 |
| Tue 17 | 0 | 0.0 | 112 ms | 0 |
| Tue 20 | 0 | 0.0 | 343 ms | 0 |
| Tue 22 | 0 | 0.0 | 329 ms | 0 |
| Wed 00 | 0 | 0.0 | 239 ms | 0 |
| Wed 02 | 0 | 0.0 | 213 ms | 0 |
| Wed 05 | 0 | 0.0 | 283 ms | 0 |
| Wed 07 | 0 | 0.0 | 404 ms | 0 |
| Wed 09 | 0 | 0.0 | 214 ms | 0 |
| Wed 11 | 0 | 0.0 | 244 ms | 0 |
| Wed 13 | 0 | 0.0 | 270 ms | 0 |
| Wed 16 | 0 | 0.0 | 273 ms | 0 |
| Wed 18 | 0 | 0.0 | 215 ms | 0 |
| Wed 20 | 0 | 0.0 | 270 ms | 0 |
| Wed 22 | 0 | 0.0 | 187 ms | 0 |
| Thu 00 | 0 | 0.0 | 473 ms | 0 |
| Thu 02 | 0 | 0.0 | 260 ms | 0 |
| Thu 04 | 0 | 0.0 | 268 ms | 0 |
| Thu 06 | 0 | 0.0 | 165 ms | 0 |
| Thu 09 | 0 | 0.0 | 263 ms | 0 |
| Thu 11 | 0 | 0.0 | 346 ms | 0 |
| Thu 13 | 0 | 0.0 | 274 ms | 0 |
| Thu 15 | 0 | 0.0 | 212 ms | 0 |
| Thu 17 | 0 | 0.0 | 212 ms | 0 |
| Thu 19 | 0 | 0.0 | 267 ms | 0 |
| Thu 21 | 0 | 0.0 | 292 ms | 0 |
| Thu 23 | 0 | 0.0 | 272 ms | 0 |
| Fri 00 | 0 | 0.0 | 307 ms | 0 |
| Fri 02 | 0 | 0.0 | 214 ms | 0 |
| Fri 04 | 0 | 0.0 | 212 ms | 0 |
| Fri 06 | 0 | 0.0 | 209 ms | 0 |
| Fri 08 | 0 | 0.0 | 270 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 Pathwright 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 Pathwright goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pathwright alerts to Slack, Discord or a webhook — free.
We track Pathwright (pathwright.com) as part of the Productivity group. Turn content, activities, and events into beautiful step-by-step learning Paths. Design courses, guide learners, and keep everyone moving forward.
Pathwright publishes an official status page at status.pathwright.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 254 ms average, 172–346 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 Pathwright incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
254 ms on average over the last 24 hours (172–346 ms).
Yes, at https://status.pathwright.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 Pathwright here at once, the problem is on Pathwright'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 Pathwright. 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.