Can’t open Notion, sign in, load a workspace, or save changes? Check Notion’s official status first, then use targeted tests to separate a service incident from a browser, account, network, or API problem.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Notion’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| notion.so | Operational | 2026-11-09 14:58 UTC |
| api.notion.com | Operational | 2026-11-09 14:58 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Notion’s official status page. official status page.

Notion availability is not always all-or-nothing. The website may open while sign-in, a specific workspace, page loading, syncing, or saving changes fails. Notion API requests and integrations can also have separate problems from the web app.
Use these signals to estimate the likely scope:
A clear status page does not rule out an account-specific, regional, browser, or network problem. Similarly, one failed API request does not by itself show that Notion is down.
Open the official Notion status page and look for an active incident, degraded component, or recovery update that matches the symptom. If the same failure occurs across devices and networks while an incident is reported, waiting for service recovery is more useful than repeatedly changing local settings.
If no incident is listed, continue with the tests below. Status information may not identify every account-specific, regional, or newly developing problem.
Confirm that you are using the intended account and authentication method. Try the sign-in flow in a private window or another browser to rule out stale cookies and an expired session. If sign-in fails across browsers and networks while other Notion pages remain reachable, investigate the account or authentication flow rather than assuming the entire service is unavailable.
Check whether the problem affects one page, one workspace, or multiple pages and workspaces. A single-page failure may be specific to that page or workspace; widespread failures are more consistent with a service, session, or connection problem. Keep the page open, protect any unsaved local work, avoid repeatedly submitting the same change, and retry after confirming that the connection is stable.
Test the API independently from the website. Review the request endpoint, authentication credentials, required headers, permissions, request format, and response status. A functioning web app does not confirm that an integration is configured correctly, and an API error alone does not prove a Notion outage. Remove credentials and other secrets from logs or screenshots before sharing diagnostics.
DNS errors, connection timeouts, refused connections, and certificate warnings can occur before Notion receives a request. Compare another network, verify that the device clock is correct, and check whether a VPN, proxy, firewall, security product, or filtered DNS service is interfering. Do not bypass certificate warnings or install untrusted certificates as a workaround.
Use the status page for service-availability information. Interpret browser, account, integration, and network errors alongside the status information rather than treating one local error as proof of a Notion-wide outage.
Every time this page loads, our server makes its own request to notion.so (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
No. This is a live, one-off connectivity check run from our own server, not Notion's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Check the official Notion status page for current incidents, affected components, and recovery updates. If no incident is listed, test another browser, device, and network to distinguish a local or account-specific problem from a wider outage.
The problem may be limited to your browser session, account, workspace access, network, DNS, VPN, or security software. Try a private window and another network before treating the issue as a Notion-wide outage.
Notion features and workspaces can fail independently. Check whether the problem affects one page or multiple pages, confirm that your connection is stable, and review the official status information. Avoid repeatedly submitting changes while saving is unreliable.
Try one refresh, a private window, another browser, and another network. Disable extensions that alter scripts or network requests. If the same failure occurs across browsers and networks, check for a Notion incident or degraded component.
The request may use an incorrect endpoint, invalid or expired credentials, missing permissions, malformed headers, or an unsupported request format. Review the API response code and request configuration separately from the availability of the Notion web app.
Repeated retries generally do not resolve a platform-side incident and may risk duplicate submissions when an action partially succeeds. Check the status updates, preserve unsaved work, and retry after recovery is reported.
This is a live connectivity check from our server, not an official statement from Notion. A down result may also reflect a regional or partial outage.