Notion had two separate problems on 13 October: a still-open disruption to real-time updates and the Notion API, and a resolved form submission error that lasted 7h 52m. Both originated on Notion's side of the connection.
Started
17:17 UTC
Duration
Lasted 8d 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.
What happened?
Notion's status page records two incidents for the day. The first started at 17:17 UTC and covers degraded performance in Notion and the Notion API, including delayed or missing real-time updates, slower page creation and updates, and failures uploading images in Notion AI. Notion's own update says users saw this during an earlier disruption around 2am PDT and again from roughly 7:30am to 8:45am PDT, meaning the problem had been running for hours before the public filing caught up. Notion applied mitigations for the real-time update piece and said it was still confirming whether the API impact had fully recovered. A second update at 21:47 UTC went further: Notion announced a planned infrastructure migration for 20 October at 2pm PDT specifically to address these real-time update disruptions, and warned that the same symptoms, plus delays adding workspace members and failures in custom agent runs, could recur during that migration. This incident carries no resolved timestamp and is still open as of that 21:47 UTC update, the last one Notion has published. The second incident, form submission errors, started at 21:19 UTC and ran for 7h 52m before Notion marked it resolved, with impact described as occurring between roughly 9:00am and 10:00am PDT. No components list was published for either incident, and no user reports came in through this window. Notion's history shows 28 incidents in the last 90 days with a median duration of 2 hours 23 minutes, so a multi-incident day like this one is not unusual for this provider.
Learning
UptimeRobot's own 30-day figures for Notion show 12 incidents with 11 resolved and a median duration of 2h 55m, which lines up with a provider that has frequent, usually short interruptions punctuated by longer ones like this real-time update problem. An external check that only pings Notion's front door can come back green while real-time sync, API calls and image uploads are all degraded underneath, because those are separate code paths and infrastructure components, not one pass or fail switch. That is exactly the shape of this incident: the page loads, but updates, API writes and uploads lag or fail depending on which part of Notion's backend you touch. Watching your own endpoint tells you your product sent the request, it does not tell you whether Notion's API answered correctly or in time. The planned migration Notion announced is a sign the underlying cause was infrastructural rather than a one-off blip, and it is scheduled to risk the same symptoms again. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.