User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
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 min ago. Last stored result reached it in 1840 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 104 ms | 0 |
| Mon 23 | 0 | 0.0 | 160 ms | 0 |
| Tue 01 | 0 | 0.0 | 64 ms | 0 |
| Tue 03 | 0 | 0.0 | 105 ms | 0 |
| Tue 05 | 0 | 0.0 | 348 ms | 0 |
| Tue 08 | 0 | 0.0 | 373 ms | 0 |
| Tue 10 | 0 | 0.0 | 340 ms | 0 |
| Tue 12 | 0 | 0.0 | 358 ms | 0 |
| Tue 14 | 0 | 0.0 | 399 ms | 0 |
| Tue 16 | 0 | 0.0 | 101 ms | 0 |
| Tue 19 | 0 | 0.0 | 236 ms | 0 |
| Tue 21 | 0 | 0.0 | 131 ms | 0 |
| Tue 23 | 0 | 0.0 | 56 ms | 0 |
| Wed 01 | 0 | 0.0 | 55 ms | 0 |
| Wed 03 | 0 | 0.0 | 332 ms | 0 |
| Wed 06 | 0 | 0.0 | 63 ms | 0 |
| Wed 08 | 0 | 0.0 | 189 ms | 0 |
| Wed 10 | 0 | 0.0 | 323 ms | 0 |
| Wed 11 | 0 | 0.0 | 55 ms | 0 |
| Wed 13 | 0 | 0.0 | 93 ms | 0 |
| Wed 16 | 0 | 0.0 | 485 ms | 0 |
| Wed 18 | 0 | 0.0 | 65 ms | 0 |
| Wed 20 | 0 | 0.0 | 55 ms | 0 |
| Wed 22 | 0 | 0.0 | 71 ms | 0 |
| Thu 00 | 0 | 0.0 | 50 ms | 0 |
| Thu 02 | 0 | 0.0 | 114 ms | 0 |
| Thu 04 | 0 | 0.0 | 108 ms | 0 |
| Thu 06 | 0 | 0.0 | 57 ms | 0 |
| Thu 09 | 0 | 0.0 | 108 ms | 0 |
| Thu 11 | 0 | 0.0 | 361 ms | 0 |
| Thu 13 | 0 | 0.0 | 67 ms | 0 |
| Thu 15 | 0 | 0.0 | 350 ms | 0 |
| Thu 17 | 0 | 0.0 | 109 ms | 0 |
| Thu 19 | 0 | 0.0 | 116 ms | 0 |
| Thu 21 | 0 | 0.0 | 54 ms | 0 |
| Thu 23 | 0 | 0.0 | 78 ms | 0 |
| Fri 01 | 0 | 0.0 | 385 ms | 0 |
| Fri 03 | 0 | 0.0 | 160 ms | 0 |
| Fri 05 | 0 | 0.0 | 100 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
| Fri 09 | 0 | 0.0 | 77 ms | 0 |
| Fri 10 | 0 | 0.0 | 92 ms | 0 |
| Fri 11 | 0 | 0.0 | 66 ms | 0 |
| Fri 13 | 0 | 0.0 | 54 ms | 0 |
| Fri 15 | 0 | 0.0 | 369 ms | 0 |
| Fri 17 | 0 | 0.0 | 263 ms | 0 |
| Fri 19 | 0 | 0.0 | 1840 ms | 0 |
| Fri 21 | 0 | 0.0 | 75 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 Morgen 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 Morgen goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Morgen alerts to Slack, Discord or a webhook — free.
We track Morgen (morgen.so) as part of the AI group. AI-powered daily planning across all your calendars and task managers. Time block, schedule meetings, and protect focus time — all in one app.
Morgen publishes an official status page at status.morgen.so; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 277 ms average, 54–1840 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 Morgen incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
277 ms on average over the last 24 hours (54–1840 ms).
Yes, at https://status.morgen.so.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Morgen here at once, the problem is on Morgen'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 Morgen. 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.