Notion logged two separate incidents on 20 October 2026, both tied to the Data & Integrations component. One blocked workspace connection installs for 20 hours, the other was a precautionary certificate update tied to a third-party certificate authority that stayed open for 143h 24m.
Started
18:46 UTC
Duration
Lasted 20h 0m
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: Data & Integrations
What happened?
Notion's status page recorded two incidents starting within 14 minutes of each other on 20 October, both filed under the Data & Integrations component. The first began at 18:46 UTC: users could not install workspace-scoped connections created by other members of their workspace, because those connections failed to appear in Browse under connection settings. Connection creators could still install their own connections, so the fault sat specifically in how shared connections were surfaced to other workspace members. Notion identified the cause by 01:15 UTC the next day and the incident closed after 20h 0m total. The second incident, opened at 19:00 UTC, was different in kind. Notion said it was responding to a security issue involving eMudhra, a third-party certificate authority used to verify secure internet connections, and that its security and engineering teams were assessing exposure and updating certificate bundles across its services. Notion explicitly stated this was a preventative security measure rather than a response to a service outage, and that it had not found evidence of compromise. That incident stayed open for 143h 24m before Notion moved it to monitoring at 00:17 UTC, having completed the certificate updates with no evidence of compromise found. No user reports were filed during the window for either incident. Notion published only two updates per incident, so the record here is thin: an opening statement and a closing or near-closing one, with no detail in between on what the identified cause actually was or how the certificate work was scoped.
Learning
The second incident is a useful reminder that not every entry on a status page means something broke for you. Notion was explicit that the eMudhra certificate work was precautionary, run in response to a vulnerability in a certificate authority rather than any observed failure in Notion itself, so a long duration on the page does not mean 143 hours of degraded service. The first incident is the more conventional case: a feature-level fault in how shared connections were displayed to non-creator workspace members, which is the kind of thing that would show up in your own product logs as installs failing silently rather than as any change in Notion's reachability. Neither incident would necessarily register on a simple uptime check against Notion's main endpoints, because both sit inside specific workflows rather than the service being down. That is exactly the gap external monitoring is built to catch: your own monitoring tells you your product is up, but it cannot tell you whether a dependency like Notion is having a quiet, feature-scoped problem on its own status page. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.