Notion Mail and Notion Calendar had degraded service for 25h 6m starting at 20:06 UTC on 12 November 2026. The fault traces back to a Microsoft Outlook outage, since Notion's Outlook integrations depend on Microsoft's infrastructure.
Started
20:06 UTC
Duration
Lasted 1d 1h
Source
IsDown
Next time
Notion is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Notion Mail, Notion Calendar
What happened?
Notion logged one incident on this day, affecting Notion Mail and Notion Calendar, two of its components. It started at 20:06 UTC and ran for 25h 6m before resolution. The only update on record is the initial one, posted at 20:06 UTC, which states that Notion was "experiencing degraded service for Outlook integrations (e.g. mail, calendar) due to the Microsoft Outlook outage" and links to Microsoft's own status page. No further updates were filed after that, so there is no record of when the degradation actually eased within the window, only the total duration once it closed. No user reports were filed during the window. Notion's status page attributes the cause directly to Microsoft rather than to its own systems, and with only one update on record, that attribution carries the full weight of what Notion has said about this incident. Over the last 90 days, Notion has logged 28 incidents with a median duration of 3 hours 51 minutes, so this one ran considerably longer than typical. Across all time, Notion averages 4.3 incidents a month over 332 total. There is no separate entry for a longest incident because this was the only one recorded on the day.
Learning
This incident sat at the intersection of two providers: Notion's Outlook integration layer failed because Microsoft's side was down, not because Notion's own infrastructure broke. If you only watch Notion's main app or API, a failure like this can pass you by, because the symptom shows up specifically in mail and calendar sync, not in Notion's core editing or page-loading paths. UptimeRobot's own 30 day figures for Notion show 11 incidents, all resolved, with a median duration of 7h 52m, which is a separate measurement from what Notion itself reports and can diverge from it depending on what each side is checking. A clean reading on your own uptime checks and a real degradation in a connected integration are both true at once, they describe different layers: your checks watch whether Notion loads, this incident was about whether Outlook mail synced. That is the general shape worth remembering, trouble in a third-party integration rarely shows up where you are looking unless you are explicitly checking that integration's own path. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.