Notion status

How we check Notion

We watch api.notion.com/v1/users from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We watch the API host that integrations and internal tools connect through, and pin the response an unauthenticated request receives rather than assuming a 2xx. The API and the web app are served separately, and it is common for one to be affected without the other, so this measures the surface most likely to break an automated workflow.

What is Notion?

Notion is a workspace built around pages that can hold documents, databases, and nested structure at once, which is why it ends up used for note-taking, project tracking, internal wikis, and increasingly as the backend for small internal tools built through its API. That last use is what makes availability worth thinking about the way an infrastructure dependency is thought about, not just as a productivity app.

The web app and the API are the first two things worth separating, since they are served independently and do not necessarily fail together. A person staring at a Notion page that will not load is having a different experience than an integration whose API calls are timing out, and either can happen while the other works normally. This page watches the API specifically, because it is the surface an automated workflow depends on and the one most likely to produce a business-impacting failure rather than an inconvenience.

Integrations add their own layer of things that look like outages and are not. An integration authenticates with a token and must also be explicitly given access to each page or database it needs, which is a separate step from the token being valid. A 401 points at the token itself, expired or revoked. A 403 points at sharing, meaning the integration exists and authenticates fine but was never granted access to the specific resource it is asking for. Both produce an error that has nothing to do with whether Notion is running.

Automations that quietly stop working are usually a permissions story rather than a platform one. Pages and databases move between sections of a workspace as teams reorganise, and an integration's access does not automatically follow a page if it is moved somewhere the integration was never shared with. The result is an automation that ran reliably for weeks and then stops with no error visible from inside Notion itself, because from the API's perspective the resource simply is not accessible anymore.

The reassuring part of depending on Notion is that an outage is a reachability problem, not a durability one. Content already saved does not disappear because the API or the app becomes briefly unreachable. The practical question after any incident is whether an edit made in the narrow window right before it fully synced, which a page's own edit history settles far better than guessing.

Frequently asked questions

Is Notion down right now?

Check the board above; it reflects our own probes against Notion's API from all five of our regions, refreshed every couple of minutes and confirmed across two regions before this page would call it down.

The Notion app will not load but this page shows it up. What should I check?

Check the API reading above specifically, because the web app and the API are served separately and either can be degraded on its own. A local network issue, a browser extension interfering with the page, or a stale cached version of the app can all block loading while both Notion's app and its API are entirely healthy elsewhere.

My integration is failing with a 401 or 403 error. Is that an outage?

No, both mean the API answered you and rejected the request. A 401 usually means the integration token is missing, expired, or was revoked, and a 403 usually means the integration has not been explicitly shared with the page or database it is trying to reach. Fixing either is a configuration change on your side, not something waiting on Notion.

Does a Notion outage delete or lose my pages?

No. An outage affects reachability, not the durability of what has already been saved. The more common data question during an incident is whether an edit made right before the outage was fully synced, which is worth checking against the page's own edit history once things recover rather than assuming the worst.

Why did my automation stop firing after working fine for weeks?

Check the integration's permissions before assuming a platform problem, since access to a specific page or database can be removed independently of the integration token itself remaining valid. A page moved into a workspace section the integration was never shared with is a common, quiet cause that produces no error visible from inside Notion.