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 2 hr ago. Last stored result reached it in 166 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 233 ms | 0 |
| Mon 21 | 0 | 0.0 | 120 ms | 0 |
| Mon 23 | 0 | 0.0 | 112 ms | 0 |
| Tue 01 | 0 | 0.0 | 71 ms | 0 |
| Tue 04 | 0 | 0.0 | 111 ms | 0 |
| Tue 06 | 0 | 0.0 | 111 ms | 0 |
| Tue 08 | 0 | 0.0 | 142 ms | 0 |
| Tue 10 | 0 | 0.0 | 96 ms | 0 |
| Tue 12 | 0 | 0.0 | 130 ms | 0 |
| Tue 14 | 0 | 0.0 | 143 ms | 0 |
| Tue 17 | 0 | 0.0 | 237 ms | 0 |
| Tue 19 | 0 | 0.0 | 166 ms | 0 |
| Tue 21 | 0 | 0.0 | 109 ms | 0 |
| Tue 23 | 0 | 0.0 | 140 ms | 0 |
| Wed 02 | 0 | 0.0 | 74 ms | 0 |
| Wed 04 | 0 | 0.0 | 184 ms | 0 |
| Wed 06 | 0 | 0.0 | 179 ms | 0 |
| Wed 08 | 0 | 0.0 | 187 ms | 0 |
| Wed 11 | 0 | 0.0 | 155 ms | 0 |
| Wed 13 | 0 | 0.0 | 181 ms | 0 |
| Wed 15 | 0 | 0.0 | 200 ms | 0 |
| Wed 17 | 0 | 0.0 | 130 ms | 0 |
| Wed 19 | 0 | 0.0 | 259 ms | 0 |
| Wed 20 | 0 | 0.0 | 221 ms | 0 |
| Wed 22 | 0 | 0.0 | 107 ms | 0 |
| Thu 00 | 0 | 0.0 | 113 ms | 0 |
| Thu 02 | 0 | 0.0 | 137 ms | 0 |
| Thu 04 | 0 | 0.0 | 120 ms | 0 |
| Thu 06 | 0 | 0.0 | 160 ms | 0 |
| Thu 08 | 0 | 0.0 | 135 ms | 0 |
| Thu 10 | 0 | 0.0 | 137 ms | 0 |
| Thu 12 | 0 | 0.0 | 100 ms | 0 |
| Thu 14 | 0 | 0.0 | 144 ms | 0 |
| Thu 17 | 0 | 0.0 | 192 ms | 0 |
| Thu 19 | 0 | 0.0 | 108 ms | 0 |
| Thu 21 | 0 | 0.0 | 200 ms | 0 |
| Thu 23 | 0 | 0.0 | 129 ms | 0 |
| Fri 01 | 0 | 0.0 | 108 ms | 0 |
| Fri 03 | 0 | 0.0 | 143 ms | 0 |
| Fri 05 | 0 | 0.0 | 127 ms | 0 |
| Fri 07 | 0 | 0.0 | 109 ms | 0 |
| Fri 09 | 0 | 0.0 | 147 ms | 0 |
| Fri 11 | 0 | 0.0 | 110 ms | 0 |
| Fri 12 | 0 | 0.0 | 116 ms | 0 |
| Fri 14 | 0 | 0.0 | 116 ms | 0 |
| Fri 16 | 0 | 0.0 | 198 ms | 0 |
| Fri 18 | 0 | 0.0 | 96 ms | 0 |
| Fri 19 | 0 | 0.0 | 166 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 Scan123 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 Scan123 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scan123 alerts to Slack, Discord or a webhook — free.
Scan123, at scan123.com, is one of the Productivity services we monitor. Scan123 helps you move from an inefficient paper-filled office to a simple electronic document management system to save time and money. Request your free demo today!
Scan123 publishes an official status page at status.scan123.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 136 ms average, 96–200 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 Scan123 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
136 ms on average over the last 24 hours (96–200 ms).
Yes, at https://status.scan123.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 Scan123 here at once, the problem is on Scan123'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 Scan123. 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.