Notion's Core Services and page editing slowed for 38 minutes on 5 October, a fault on Notion's side rather than anything in your own setup. Notion identified the issue at 12:26 and the incident closed without a separate recovery notice on record.
Started
12:26 UTC
Duration
Lasted 38m
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: Core Services, View and edit content
What happened?
Notion logged one incident on 5 October, starting at 12:26 UTC and lasting 38 minutes. The title Notion gave it was "Page loading and editing may be slower than expected", covering the Core Services and View and edit content components. Only one update was posted, at 12:26, saying Notion had identified the issue and was taking steps to restore normal performance, with a promise to update again after confirming recovery. No such follow-up appears in the record, so you are left with the identified update and the 38 minute duration as the only facts on file. No user reports were filed during the window. Over the past 90 days Notion has logged 28 incidents with a median duration of 1 hour 35 minutes, so this one resolved faster than Notion's own recent average. Across all time Notion has recorded 319 incidents, averaging 4.2 per month. Notion's status page does not say what caused the slowdown, and nothing on record explains why it cleared when it did.
Learning
UptimeRobot's own 30 day figures for Notion show 10 incidents, all resolved, with a median duration of 43m, a pattern that lines up with this one rather than contradicting it. A slowdown in page loading and editing is a performance problem inside Notion's application layer, not a case of servers going fully dark, so an external check hitting Notion's front door can come back green while your own document is still crawling to redraw. That is because uptime checks and in-app responsiveness measure different things: one asks whether the service answers at all, the other asks whether it answers fast enough to use. When Notion identifies an issue but never files a recovery note, you are stuck guessing when things actually got better unless you were watching the symptom yourself. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
