Some connected content results unavailable in Notion AI
Fix has been deployed for this.
The latest update from Notion.
State
Resolved
Started
45 d ago
2026-09-17 14:07 UTC
Lasted
4 days
until 2026-09-21 07:14 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
14 h 32 min 16%
Identified
3 days 84%
Updates
Times in UTCAs posted by Notion
Fix has been deployed for this.
We have identified the cause of the AI Connector sync delays and implemented a fix. Syncs are recovering, but some users may continue to experience delayed or missing results in Notion AI. We are currently monitoring the recovery and will provide another update when more information is available.
Some users may not see results from connected content in Notion AI. We’re investigating and will share another update within two hours.
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
26× 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