Degraded performance in Notion and the Notion API

What to do

• Check whether your product depends on Notion. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 8d 1h it lasted.

  Anything that failed between 2026-10-13 17:17 UTC and 2026-10-21 18:56 UTC may need a replay.

• Subscribe to Notion's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=notion works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Notion 4

1. monitoringOct 13, 2026, 5:17 PM 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.

   provider

2. monitoringOct 15, 2026, 9:47 PM 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.

   provider

3. monitoringOct 21, 2026, 5:23 AM 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.

   provider

4. resolvedOct 21, 2026, 6:56 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.