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.
The latest update from Notion.
State
Resolved
Started
12 d ago
2026-10-20 18:46 UTC
Lasted
19 h 57 min
until 2026-10-21 14:43 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
6 h 28 min 32%
Identified
13 h 29 min 68%
Updates
Times in UTCAs posted by Notion
The issue has been resolved. Thank you for your patience while we worked on a fix.
We have identified the cause of the issue preventing users from installing connections created by other members of their workspace and are working on a fix. Connection creators can still install their own connections.
Users are unable to install workspace-scoped connections created by other members of their workspace because these connections are not appearing in Browse in connection settings. Connection creators can still install their own connections. We are investigating and working on a fix.
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
5.9× 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·Some Notion Agent requests may stop before completion
The issue causing some Notion Agent requests to stop before completing has been resolved. Notion Agent is operating normally. Thank you for your patience.
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