Datvero automation observatory · www.notion-status.com
No. Notion's status page reports all systems operational for Notion: View and edit content, Databases, Notion API and 16 other components (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
Read from Notion's official status API at November 6, 2026, 18:10 UTC. Datvero republishes what Notion states; it is not an independent uptime measurement.
From September 2 to November 6, 2026, www.notion-status.com lists 25 incidents: 1 critical, 3 major, 11 minor and 10 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 2.9 h. Longest: “Some connected content results unavailable in Notion AI” (September 17, 2026), 3.7 days. In the last 30 days: 9 incidents, 3 of them major or critical.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
No. Notion's status page reports all systems operational for Notion: View and edit content, Databases, Notion API and 16 other components (checked November 6, 2026, 18:10 UTC; this page refreshes every 5 minutes).
From September 2 to November 6, 2026, www.notion-status.com lists 25 incidents: 1 critical, 3 major, 11 minor and 10 with no impact (the vendor's own classification). Median time from first post to resolution, impact incidents only: 2.9 h. Longest: “Some connected content results unavailable in Notion AI” (September 17, 2026), 3.7 days. In the last 30 days: 9 incidents, 3 of them major or critical.
Notion publishes it at https://www.notion-status.com/. This page republishes its public feed every 5 minutes with timestamps. Datvero is not affiliated with Notion.
When the status page is green but your integration fails, read the response. Requests that exceed a Notion API limit return the error code rate_limited with HTTP 429 and a Retry-After header; wait for that delay before retrying. That is a limit, not an outage.
The status page lists what Notion has declared. If it is green and you still see errors, read the error code, retry with a growing delay, and check whether the problem is specific to your account, your region or one integration. A green page does not prove that every request to Notion succeeds.
Retry with a growing delay, send failures to an error workflow, and get alerted when runs stop succeeding. In n8n, every node has a Retry On Fail setting; Make has Break error handlers that retry incomplete executions; Zapier can replay failed runs with Autoreplay. Datvero watches the runs of your n8n, Make and Zapier workflows and alerts you when they fail, whatever the cause.
Method: Notion's public status API (www.notion-status.com/api/v2) is read every 5 minutes, its incident list every 15 minutes, and each incident is kept with its official timestamps. Durations run from the first post to the resolved post. Machine readable copy: services.json. HTTP codes: Notion developers, Request limits. Official source: https://www.notion-status.com/.
Statuses, incident names and texts belong to Notion. Datvero is not affiliated with Notion. A green status page does not mean every workflow that calls Notion succeeds.