Notion 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 notion.so. Compare the regional responses with the problem you see in Notion.
Find Notion 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
A Notion page, database query, export and synchronisation can fail separately.
The checker above requests notion.so from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Notion action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
For other document and collaboration tools, compare: Is Overleaf Down?, Is Box Down?, Is Docusign Down?.
Separate Notion workspace access from integration or documentation access using these checks: Notion API status check, Notion Developers status check, Notion Status status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app 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 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.
Workspace/page reference privately, failed operation, client version and last saved 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.
These are troubleshooting comparisons, not claims that Notion is currently experiencing a particular incident.
Compare a small page with the affected database or workspace and preserve unsaved text.
Ask an authorised collaborator to check the same page state before reloading; distinguish lost permission from a load error.
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 seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open 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 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 support.
Run the notion.so check and compare its original timestamps and responses with your actual error. A Notion page, database query, export and synchronisation can fail separately.
Use the community buttons on this page to share whether the service works for you. For help from Notion, use the official help/reporting resource linked above. Keep unsaved page content safe and use workspace-specific support context.
Compare a small page with the affected database or workspace and preserve unsaved text. Ask an authorised collaborator to check the same page state before reloading; distinguish lost permission from a load error.
Workspace/page reference privately, failed operation, client version and last saved time.