Notion · Identified
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Notion status

Notion · Incident Io
Identified
incident.io reports 1 ongoing incident(s): identified.
App, API and related services
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

Some connected content results unavailable in Notion AI

We have identified the cause of the AI Connector sync delays and implemented a fix. Syncs are recovering, but some users may continue to experience delayed or missing results in Notion AI. We are currently monitoring the recovery and will provide another update when more information is available.

Status identified Impact degraded Updated

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
19
Retained
19
Affected retained
1
Projection scope: complete · 19 retained of 19 reported components across 3 source groups.
Login and user accounts Group: Core Services Operational
View and edit content Group: Core Services Operational
Databases Group: Core Services Operational
Search Group: Core Services Operational
Notifications Group: Core Services Operational
Notion Agent Group: Notion AI Degraded
Enterprise Search Group: Notion AI Operational
Custom Agents Group: Notion AI Operational
AI Meeting Notes Group: Notion AI Operational
Notion API Group: Developer Platform Operational
Notion MCP Group: Developer Platform Operational
Notion Workers Group: Developer Platform Operational
Data & Integrations Group: Developer Platform Operational
Notion Apps Operational
Notion Calendar Operational
Notion Mail Operational
Notion Sites Operational
Marketplace Operational
Administration Operational

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Degraded
HTTP 200 · 258.06 ms feed latency
Degraded
HTTP 200 · 216.95 ms feed latency
Degraded
HTTP 200 · 264.7 ms feed latency
Degraded
HTTP 200 · 272.37 ms feed latency
Degraded
HTTP 200 · 282.26 ms feed latency
Degraded
HTTP 200 · 350.35 ms feed latency
Degraded
HTTP 200 · 316.09 ms feed latency
Degraded
HTTP 200 · 313.22 ms feed latency
Degraded
HTTP 200 · 288.54 ms feed latency
Degraded
HTTP 200 · 294.17 ms feed latency

Collection details

Provider adapter
Incident Io
Feed response
HTTP 200
Feed latency
303.55 ms