User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
nirvanahq.com · Cloud & developer
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 8 min ago. Last stored result reached it in 336 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 220 ms | 0 |
| Mon 17 | 0 | 0.0 | 275 ms | 0 |
| Mon 19 | 0 | 0.0 | 271 ms | 0 |
| Mon 21 | 0 | 0.0 | 309 ms | 0 |
| Mon 23 | 0 | 0.0 | 333 ms | 0 |
| Tue 01 | 0 | 0.0 | 253 ms | 0 |
| Tue 03 | 0 | 0.0 | 186 ms | 0 |
| Tue 05 | 0 | 0.0 | 374 ms | 0 |
| Tue 08 | 0 | 0.0 | 168 ms | 0 |
| Tue 10 | 0 | 0.0 | 375 ms | 0 |
| Tue 12 | 0 | 0.0 | 288 ms | 0 |
| Tue 14 | 0 | 0.0 | 304 ms | 0 |
| Tue 16 | 0 | 0.0 | 248 ms | 0 |
| Tue 19 | 0 | 0.0 | 158 ms | 0 |
| Tue 21 | 0 | 0.0 | 284 ms | 0 |
| Tue 23 | 0 | 0.0 | 373 ms | 0 |
| Wed 01 | 0 | 0.0 | 437 ms | 0 |
| Wed 04 | 0 | 0.0 | 319 ms | 0 |
| Wed 06 | 0 | 0.0 | 325 ms | 0 |
| Wed 08 | 0 | 0.0 | 309 ms | 0 |
| Wed 10 | 0 | 0.0 | 231 ms | 0 |
| Wed 12 | 0 | 0.0 | 383 ms | 0 |
| Wed 13 | 0 | 0.0 | 156 ms | 0 |
| Wed 15 | 0 | 0.0 | 369 ms | 0 |
| Wed 17 | 0 | 0.0 | 362 ms | 0 |
| Wed 19 | 0 | 0.0 | 736 ms | 0 |
| Wed 21 | 0 | 0.0 | 960 ms | 0 |
| Wed 23 | 0 | 0.0 | 309 ms | 0 |
| Thu 01 | 0 | 0.0 | 342 ms | 0 |
| Thu 03 | 0 | 0.0 | 295 ms | 0 |
| Thu 05 | 0 | 0.0 | 359 ms | 0 |
| Thu 08 | 0 | 0.0 | 325 ms | 0 |
| Thu 10 | 0 | 0.0 | 424 ms | 0 |
| Thu 12 | 0 | 0.0 | 300 ms | 0 |
| Thu 14 | 0 | 0.0 | 301 ms | 0 |
| Thu 16 | 0 | 0.0 | 360 ms | 0 |
| Thu 18 | 0 | 0.0 | 365 ms | 0 |
| Thu 20 | 0 | 0.0 | 237 ms | 0 |
| Thu 22 | 0 | 0.0 | 313 ms | 0 |
| Thu 23 | 0 | 0.0 | 240 ms | 0 |
| Fri 01 | 0 | 0.0 | 272 ms | 0 |
| Fri 03 | 0 | 0.0 | 261 ms | 0 |
| Fri 06 | 0 | 0.0 | 240 ms | 0 |
| Fri 08 | 0 | 0.0 | 260 ms | 0 |
| Fri 10 | 0 | 0.0 | 208 ms | 0 |
| Fri 12 | 0 | 0.0 | 335 ms | 0 |
| Fri 14 | 0 | 0.0 | 203 ms | 0 |
| Fri 16 | 0 | 0.0 | 336 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 Nirvana 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 Nirvana goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nirvana alerts to Slack, Discord or a webhook — free.
Nirvana is listed in our Cloud & developer category and checked at nirvanahq.com. Nirvana is the calm to-do list app built for Getting Things Done®. Clear your mind, decide what matters, and make steady progress.
Nirvana publishes an official status page at status.nirvanahq.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 273 ms average, 203–365 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 Nirvana incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
273 ms on average over the last 24 hours (203–365 ms).
Yes, at https://status.nirvanahq.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Nirvana here at once, the problem is on Nirvana'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 Nirvana. 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.