outages.live
Live
NotionIncident · 2026-10-13 17:17 UTC

Degraded performance in Notion and the Notion API

ResolvedOfficial update

The migration to our new infrastructure completed without customer impact, and service remains stable. This incident is resolved.

The latest update from Notion.

State

Resolved

Started

19 d ago

2026-10-13 17:17 UTC

Lasted

8 days

until 2026-10-21 18:56 UTC

Worst impact

Notice

Timeline

4 updates
Oct 13Oct 15Oct 17Oct 19Oct 21
NoticeUpdate postedDates in UTC

Monitoring

8 days 100%

Updates

Times in UTC

As posted by Notion

Resolved2026-10-21 18:56 UTC

The migration to our new infrastructure completed without customer impact, and service remains stable. This incident is resolved.

Monitoring2026-10-21 05:23 UTC

The infrastructure migration to improve service reliability is now in progress. We are observing stability before gracefully retiring the old cluster and completing the migration. We will share further updates as the migration progresses or the completion estimate changes.

Monitoring2026-10-15 21:47 UTC

We are preparing an infrastructure migration to address the recent disruptions to real-time updates in Notion and improve service reliability. The production migration is planned to begin next Tuesday, October 20, at 2pm PDT. During the migration, users may experience: • Delayed or missing real-time updates in Notion. • Slower page creation and updates through the Notion API and MCP. • Failures uploading screenshots in Notion AI chats. • Failures or delays in custom agent runs. • Delays when adding members to workspaces. Our team will closely monitor these features during the migration. We apologize for any disruption and appreciate your patience.

Monitoring2026-10-13 17:17 UTC

Some users experienced delayed or missing real-time updates in Notion during an earlier disruption around 2am PDT on October 13 and again from approximately 7:30am to 8:45am PDT. Degraded performance for page creation, updates in the Notion API and image uploads to Notion AI has also been reported. We have applied mitigations for the real-time update disruption and are monitoring recovery. We are confirming whether the reported API impact has fully recovered. We apologize for the disruption.

Notion in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

24

Days with an incident

29

Median duration

3 h 23 min

This incident

57× the median

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

8 days
median 3 h 23 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.

Resolvedresolved 9 d ago

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

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

Resolvedresolved 6 d ago

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.

Resolvedresolved 10 d ago

Notion·Security update: Preventative certificate security measures

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

Resolvedresolved 6 d ago

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.

Resolvedresolved 11 d ago

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

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane