- Level
- confirmed
- Worst impact
- Degraded
- Components
- View and edit content
- Down Index
- 18of 100
What to do
Check whether you use Notion View and edit content. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 48m it lasted.
Anything that failed between 2026-08-31 09:20 UTC and 2026-08-31 10:08 UTC may need a replay.Subscribe to Notion's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=notion works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Notion 3
- investigating
Some users may experience increased latency or errors when syncing blocks or editing content. We are investigating the issue and working to restore normal performance.
provider
- monitoring
We have mitigated the issue affecting syncing and editing content, and performance has recovered. We are monitoring to ensure service remains stable.
provider
- resolved
The issue affecting syncing and editing content has been resolved. Performance has recovered and services are operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-bf75cf1f80
Is Notion still down?
No, this incident was resolved 2026-08-31 10:08 UTC. For Notion's live state, see https://down.guide/notion.
How long did it last?
48m, from 2026-08-31 09:20 UTC to 2026-08-31 10:08 UTC, by the times Notion posted.
What was affected?
Notion named View and edit content.
What caused it?
Notion hasn't published a root cause. If it does, it shows here.
Where does this come from?
Notion's official status page, https://www.notion-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.