Skip to content

Outage tracker

Notion: incident history

The last 24 hours in detail, Notion's declared incident record, and our regional check results beside it.

← Back to Notion's check readings

Email me when Notion reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Notion's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Notion's own status page declared. Below it, any public chatter we saw about Notion and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Notion's own status page declared. Three records side by side; none of them changes another.

Our probes, web (primary)
Our probes, login and user accounts
Our probes, marketplace
Our probes, notion calendar
Our probes, notion mail
Our probes, notion mcp
Unverified user reportsNo reports about Notion in the last 24 hours, which is not evidence that nothing is wrong.
Notion's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Notion's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Notion next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

  • Bluesky posts1 in the last hour (prior day averaged 0.2/hour)

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East99.95%12766
US-West99.98%12502
Europe99.95%12391
Asia-Pacific99.89%12028
US-Central99.98%4601
Canada99.98%4601
UK99.96%4600
Southeast Asia99.96%4569
Australia99.89%4563
South America99.52%4591

Their declared record

Notion's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Users unable to access NotionMajor outage
Oct 23, 2026, 3:38 AM UTC to Oct 23, 2026, 4:01 AM UTC (23 min)resolved
their latest update (Oct 23, 2026, 6:44 AM UTC): 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.
PHP2Shell (CVE-2026-109618, CVE-2026-109619)All systems operational
Oct 23, 2026, 12:14 AM UTC to Oct 26, 2026, 6:24 PM UTC (3d 18h)resolved
their latest update (Oct 26, 2026, 6:24 PM UTC): Please visit our Security Advisories page at https://www.notion.com/security/advisories for any future updates.
Notion MCP query_data_source tool is temporarily unavailable in Claude clientsPartial outage
Oct 22, 2026, 3:23 AM UTC to Oct 22, 2026, 4:42 AM UTC (1h 19m)resolved
their latest update (Oct 22, 2026, 4:42 AM UTC): This issue has been resolved. The Notion MCP query_data_source tool is available again in Claude clients.
Security update: Preventative certificate security measuresAll systems operational
Oct 20, 2026, 7:00 PM UTC to Oct 26, 2026, 6:23 PM UTC (5d 23h)resolved
their latest update (Oct 26, 2026, 6:23 PM UTC): Please visit our Security Advisories page at https://www.notion.com/security/advisories for any future updates.
Unable to install connections created by other workspace membersPartial outage
Oct 20, 2026, 6:46 PM UTC to Oct 21, 2026, 2:43 PM UTC (19h 57m)resolved
their latest update (Oct 21, 2026, 2:43 PM UTC): The issue has been resolved. Thank you for your patience while we worked on a fix.
Some Notion Agent requests may stop before completionMinor incident
Oct 18, 2026, 11:54 AM UTC to Oct 18, 2026, 3:51 PM UTC (3h 57m)resolved
their latest update (Oct 18, 2026, 3:51 PM UTC): The issue causing some Notion Agent requests to stop before completing has been resolved. Notion Agent is operating normally. Thank you for your patience.
Cursor-powered Custom Agents unable to load Notion toolsAll systems operational
Oct 14, 2026, 10:55 PM UTC to Oct 15, 2026, 2:34 AM UTC (3h 39m)resolved
their latest update (Oct 15, 2026, 2:34 AM UTC): Between 18:00 UTC on October 12 and 00:49 UTC on October 15, some external agents could connect to Notion but couldn't use Notion tools. This issue has been resolved, and affected agents can use Notion tools again.
Form submission issues (resolved)All systems operational
Oct 13, 2026, 9:19 PM UTC to Oct 14, 2026, 5:08 AM UTC (7h 49m)resolved
their latest update (Oct 14, 2026, 5:08 AM UTC): Form submissions are working normally.
Degraded performance in Notion and the Notion APIAll systems operational
Oct 13, 2026, 5:17 PM UTC to Oct 21, 2026, 6:56 PM UTC (8d 1h)resolved
their latest update (Oct 21, 2026, 6:56 PM UTC): The migration to our new infrastructure completed without customer impact, and service remains stable. This incident is resolved.
Delayed live updates in pages and databasesMinor incident
Oct 6, 2026, 9:49 AM UTC to Oct 6, 2026, 12:43 PM UTC (2h 54m)resolved
their latest update (Oct 6, 2026, 12:43 PM UTC): The issue affecting live updates in Notion pages and databases has been resolved. Edits from collaborators should now appear automatically.

Showing the 10 most recent of 38 incidents Notion has declared in the history we hold.

These entries are Notion's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

Notion's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.