outages.live
Live
NotionIncident ·

Some Notion Agent sessions may hang or stop updating

ResolvedOfficial update
0

Some Notion Agent sessions hung or stopped updating, so new responses did not appear in the chat. Notion identified the issue and stated that refreshing the page restored the session. Notion reported that the incident is resolved. It lasted about 2 hours and 20 minutes.

State

Resolved

Started

Lasted

2 h 20 min

Worst impact

Partial outage

Timeline

2 updates
19:5420:2921:0421:3922:14
Partial outageUpdate postedTimes in UTC

Identified

2 h 20 min 100%

Updates

Times in UTC

As posted by Notion

Resolved

The issue affecting Notion Agent sessions has been resolved

Identified

Some Notion Agent sessions may hang or stop updating, so new responses may not appear in the chat. Refreshing the page restores the session.

Notion in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

25

Days with an incident

30

Median duration

3 h 6 min

This incident

25% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

8 days
median 3 h 6 min
90 days agoToday

Other Notion incidents

All incidents

Notion·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.

Resolved

Notion·PHP2Shell (CVE-2026-109618, CVE-2026-109619)

Please visit our Security Advisories page at for any future updates.

Resolved

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.

Resolved

Notion·Security update: Preventative certificate security measures

Please visit our Security Advisories page at for any future updates.

Resolved

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.

Resolved

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.

Prompt
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.live/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.

RSS
https://outages.live/feed.xml?providers=notion
Slack
/feed subscribe https://outages.live/feed.xml?providers=notion

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane