Unexpected workspace verification banner displayed to some users
This issue has been resolved. The unexpected workspace verification banner is no longer being displayed, and this issue did not indicate that any workspaces were compromised. If the banner is still visible, please reload the page or restart the Notion app. We apologize for the confusion and concern this caused.
The latest update from Notion.
State
Resolved
Started
52 d ago
2026-09-10 01:36 UTC
Lasted
43 min
until 2026-09-10 02:20 UTC
Worst impact
Notice
Timeline
3 updatesIdentified
10 min 24%
Monitoring
33 min 76%
Updates
Times in UTCAs posted by Notion
This issue has been resolved. The unexpected workspace verification banner is no longer being displayed, and this issue did not indicate that any workspaces were compromised. If the banner is still visible, please reload the page or restart the Notion app. We apologize for the confusion and concern this caused.
The issue has been mitigated, and the unexpected workspace verification banner is no longer being displayed. This issue did not indicate that any workspaces were compromised. If the banner is still visible, please reload the page or restart the Notion app to make it disappear. We apologize for the confusion and concern this may have caused. We will continue monitoring the situation.
We're investigating an issue where some users may see an unexpected banner asking them to confirm whether they recognize their workspace. This does not indicate that the workspace has been compromised. Please do not select "No, leave workspace", as this will remove you from the workspace. You can continue using Notion while we work to resolve the issue.
Notion in the last 90 days
Full historyIncidents in 90 days
24
Days with an incident
29
Median duration
3 h 23 min
This incident
79% shorter than the median
Other Notion incidents
All incidentsNotion·Users unable to access Notion
The issue affecting access to Notion has been resolved. Signing in, loading pages, and viewing and editing content are working normally again. Thank you for your patience.
Notion·PHP2Shell (CVE-2026-109618, CVE-2026-109619)
Please visit our Security Advisories page at for any future updates.
Notion·Notion MCP query_data_source tool is temporarily unavailable in Claude clients
This issue has been resolved. The Notion MCP query_data_source tool is available again in Claude clients.
Notion·Security update: Preventative certificate security measures
Please visit our Security Advisories page at for any future updates.
Notion·Unable to install connections created by other workspace members
The issue has been resolved. Thank you for your patience while we worked on a fix.
Follow Notion
Your coding agent knows when Notion is down, and tells you when a failure is theirs, not yours. You can also get Notion incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "notion" and tell me if Notion has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=notion/feed subscribe https://outages.cc/feed.xml?providers=notionFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane