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 19 min ago. Last stored result reached it in 218 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 09:15 | 0 | 0.0 | 144 ms | 0 |
| 11:15 | 0 | 0.0 | 229 ms | 0 |
| 13:15 | 0 | 0.0 | 138 ms | 0 |
| 15:30 | 0 | 0.0 | 247 ms | 0 |
| 17:30 | 0 | 0.0 | 225 ms | 0 |
| 19:30 | 0 | 0.0 | 97 ms | 0 |
| 21:30 | 0 | 0.0 | 169 ms | 0 |
| 23:30 | 0 | 0.0 | 182 ms | 0 |
| 01:45 | 0 | 0.0 | 146 ms | 0 |
| 03:45 | 0 | 0.0 | 238 ms | 0 |
| 06:00 | 0 | 0.0 | 213 ms | 0 |
| 08:00 | 0 | 0.0 | 218 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 Scholarcy 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 Scholarcy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scholarcy alerts to Slack, Discord or a webhook — free.
Scholarcy, at scholarcy.com, is one of the Productivity services we monitor. Summarize anything, understand complex research, and organise your knowledge with Scholarcy.
Scholarcy publishes an official status page at status.scholarcy.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: 187 ms average, 97–247 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Scholarcy incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
187 ms on average over the last 24 hours (97–247 ms).
Yes, at https://status.scholarcy.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 Scholarcy here at once, the problem is on Scholarcy'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 Scholarcy. 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.