Notion reported "Issues managing email addresses and aliases" on its status page at 2026-09-11 17:23 UTC.

Notion did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-11 17:23 UTC and ended at 2026-09-11 20:04 UTC. It lasted 2 h 41 min.

How do I get alerts for Notion?

Subscribe to the Notion live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Notion. outages.live reads it every few minutes and keeps every update.

NotionIncident · 2026-09-11 17:23 UTC

Issues managing email addresses and aliases

ResolvedOfficial update

This issue is now resolved!

The latest update from Notion.

State

Resolved

Started

51 d ago

2026-09-11 17:23 UTC

Lasted

2 h 41 min

until 2026-09-11 20:04 UTC

Worst impact

Partial outage

Timeline

2 updates

17:2318:0318:4319:2420:04

Partial outageUpdate postedTimes in UTC

Identified

2 h 41 min 100%

Updates

Times in UTC

As posted by Notion

Resolved2026-09-11 20:04 UTC

This issue is now resolved!

Identified2026-09-11 17:23 UTC

We are investigating an issue affecting some users who attempt to manage email addresses or add an alias in account settings. Our team is working to restore normal functionality.

Notion in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

3 h 23 min

This incident

21% 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 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