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 41 min ago. Last stored result reached it in 1192 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 372 ms | 0 |
| Mon 17 | 0 | 0.0 | 1497 ms | 0 |
| Mon 19 | 0 | 0.0 | 462 ms | 0 |
| Mon 21 | 0 | 0.0 | 408 ms | 0 |
| Mon 23 | 0 | 0.0 | 862 ms | 0 |
| Tue 01 | 0 | 0.0 | 461 ms | 0 |
| Tue 03 | 0 | 0.0 | 879 ms | 0 |
| Tue 05 | 0 | 0.0 | 867 ms | 0 |
| Tue 07 | 0 | 0.0 | 694 ms | 0 |
| Tue 10 | 0 | 0.0 | 495 ms | 0 |
| Tue 12 | 0 | 0.0 | 470 ms | 0 |
| Tue 14 | 0 | 0.0 | 798 ms | 0 |
| Tue 16 | 0 | 0.0 | 1392 ms | 0 |
| Tue 18 | 0 | 0.0 | 553 ms | 0 |
| Tue 21 | 0 | 0.0 | 588 ms | 0 |
| Tue 23 | 0 | 0.0 | 1137 ms | 0 |
| Wed 01 | 0 | 0.0 | 674 ms | 0 |
| Wed 03 | 0 | 0.0 | 501 ms | 0 |
| Wed 06 | 0 | 0.0 | 1139 ms | 0 |
| Wed 08 | 0 | 0.0 | 542 ms | 0 |
| Wed 10 | 0 | 0.0 | 727 ms | 0 |
| Wed 12 | 0 | 0.0 | 800 ms | 0 |
| Wed 14 | 0 | 0.0 | 705 ms | 0 |
| Wed 17 | 0 | 0.0 | 399 ms | 0 |
| Wed 19 | 0 | 0.0 | 594 ms | 0 |
| Wed 21 | 0 | 0.0 | 547 ms | 0 |
| Wed 23 | 0 | 0.0 | 724 ms | 0 |
| Thu 01 | 0 | 0.0 | 653 ms | 0 |
| Thu 03 | 0 | 0.0 | 692 ms | 0 |
| Thu 05 | 0 | 0.0 | 844 ms | 0 |
| Thu 08 | 0 | 0.0 | 176 ms | 0 |
| Thu 10 | 0 | 0.0 | 595 ms | 0 |
| Thu 12 | 0 | 0.0 | 532 ms | 0 |
| Thu 14 | 0 | 0.0 | 529 ms | 0 |
| Thu 16 | 0 | 0.0 | 859 ms | 0 |
| Thu 18 | 0 | 0.0 | 678 ms | 0 |
| Thu 20 | 0 | 0.0 | 577 ms | 0 |
| Thu 22 | 0 | 0.0 | 757 ms | 0 |
| Fri 00 | 0 | 0.0 | 723 ms | 0 |
| Fri 02 | 0 | 0.0 | 475 ms | 0 |
| Fri 04 | 0 | 0.0 | 480 ms | 0 |
| Fri 06 | 0 | 0.0 | 633 ms | 0 |
| Fri 08 | 0 | 0.0 | 572 ms | 0 |
| Fri 11 | 0 | 0.0 | 863 ms | 0 |
| Fri 12 | 0 | 0.0 | 1243 ms | 0 |
| Fri 13 | 0 | 0.0 | 882 ms | 0 |
| Fri 15 | 0 | 0.0 | 1018 ms | 0 |
| Fri 17 | 0 | 0.0 | 1192 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 Notesnook 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 Notesnook goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Notesnook alerts to Slack, Discord or a webhook — free.
We track Notesnook (notesnook.com) as part of the Productivity group. Express yourself with freedom — no spying, no tracking, only private notes. Unlike Evernote and other note apps, your data is yours alone.
Notesnook publishes an official status page at status.notesnook.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 776 ms average, 475–1243 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 Notesnook incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
776 ms on average over the last 24 hours (475–1243 ms).
Yes, at https://status.notesnook.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 Notesnook here at once, the problem is on Notesnook'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 Notesnook. 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.