Notion Status service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Run a live reachability check for status.notion.so. Compare the regional responses with the problem you see in Notion Status.
Find Notion Status help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
The Notion status page describes incident scope; it does not read or edit your workspace.
The checker above requests status.notion.so from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Notion Status action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Separate Notion workspace access from integration or documentation access using these checks: Notion status check, Notion API status check, Notion Developers status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Keep unsaved page content safe and use workspace-specific support context.
Open the website in your browser and compare it with the result above.
Open Notion Status help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Status/incident URL, affected Notion feature, client and UTC time.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Notion Status.
These are troubleshooting comparisons, not claims that Notion Status is currently experiencing a particular incident.
Compare the affected page/API action with the named incident and its update time.
If the dashboard is unavailable or shows recovery, check the actual failed operation again before declaring it resolved.
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Notion Status seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open status.notion.so in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Notion Status issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Notion Status support.
Run the status.notion.so check and compare its original timestamps and responses with your actual error. The Notion status page describes incident scope; it does not read or edit your workspace.
Use the community buttons on this page to share whether the service works for you. For help from Notion Status, use the official help/reporting resource linked above. Keep unsaved page content safe and use workspace-specific support context.
Compare the affected page/API action with the named incident and its update time. If the dashboard is unavailable or shows recovery, check the actual failed operation again before declaring it resolved.
Status/incident URL, affected Notion feature, client and UTC time.