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 20 min ago. Last stored result reached it in 268 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 600 ms | 0 |
| Mon 19 | 0 | 0.0 | 280 ms | 0 |
| Mon 21 | 0 | 0.0 | 238 ms | 0 |
| Mon 23 | 0 | 0.0 | 264 ms | 0 |
| Tue 01 | 0 | 0.0 | 227 ms | 0 |
| Tue 03 | 0 | 0.0 | 257 ms | 0 |
| Tue 06 | 0 | 0.0 | 184 ms | 0 |
| Tue 08 | 0 | 0.0 | 241 ms | 0 |
| Tue 10 | 0 | 0.0 | 221 ms | 0 |
| Tue 12 | 0 | 0.0 | 199 ms | 0 |
| Tue 14 | 0 | 0.0 | 211 ms | 0 |
| Tue 16 | 0 | 0.0 | 232 ms | 0 |
| Tue 19 | 0 | 0.0 | 304 ms | 0 |
| Tue 21 | 0 | 0.0 | 236 ms | 0 |
| Tue 23 | 0 | 0.0 | 209 ms | 0 |
| Wed 01 | 0 | 0.0 | 235 ms | 0 |
| Wed 04 | 0 | 0.0 | 215 ms | 0 |
| Wed 06 | 0 | 0.0 | 236 ms | 0 |
| Wed 08 | 0 | 0.0 | 215 ms | 0 |
| Wed 10 | 0 | 0.0 | 223 ms | 0 |
| Wed 13 | 0 | 0.0 | 259 ms | 0 |
| Wed 15 | 0 | 0.0 | 296 ms | 0 |
| Wed 17 | 0 | 0.0 | 248 ms | 0 |
| Wed 19 | 0 | 0.0 | 250 ms | 0 |
| Wed 21 | 0 | 0.0 | 223 ms | 0 |
| Wed 23 | 0 | 0.0 | 281 ms | 0 |
| Thu 02 | 0 | 0.0 | 216 ms | 0 |
| Thu 04 | 0 | 0.0 | 222 ms | 0 |
| Thu 05 | 0 | 0.0 | 216 ms | 0 |
| Thu 07 | 0 | 0.0 | 3072 ms | 0 |
| Thu 09 | 0 | 0.0 | 254 ms | 0 |
| Thu 11 | 0 | 0.0 | 245 ms | 0 |
| Thu 13 | 0 | 0.0 | 211 ms | 0 |
| Thu 15 | 0 | 0.0 | 220 ms | 0 |
| Thu 17 | 0 | 0.0 | 267 ms | 0 |
| Thu 19 | 0 | 0.0 | 256 ms | 0 |
| Thu 21 | 0 | 0.0 | 301 ms | 0 |
| Thu 23 | 0 | 0.0 | 214 ms | 0 |
| Fri 01 | 0 | 0.0 | 230 ms | 0 |
| Fri 03 | 0 | 0.0 | 208 ms | 0 |
| Fri 05 | 0 | 0.0 | 211 ms | 0 |
| Fri 07 | 0 | 0.0 | 285 ms | 0 |
| Fri 09 | 0 | 0.0 | 271 ms | 0 |
| Fri 11 | 0 | 0.0 | 214 ms | 0 |
| Fri 12 | 0 | 0.0 | 221 ms | 0 |
| Fri 14 | 0 | 0.0 | 249 ms | 0 |
| Fri 16 | 0 | 0.0 | 292 ms | 0 |
| Fri 17 | 0 | 0.0 | 268 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 Papershift 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 Papershift goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Papershift alerts to Slack, Discord or a webhook — free.
Papershift, at papershift.com, is one of the Productivity services we monitor. Digitales Personalmanagement für kleine & große Teams. Mit der Papershift HR Software online Dienstpläne erstellen & Arbeitszeiten erfassen. Jetzt testen!
Papershift publishes an official status page at status.papershift.com; 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: 249 ms average, 208–301 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Papershift incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
249 ms on average over the last 24 hours (208–301 ms).
Yes, at https://status.papershift.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 Papershift here at once, the problem is on Papershift'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 Papershift. 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.