User-specific data accessible to the wrong users within the same workspace

Update timeline

1. identified Mar 24, 2026, 04:02 AM UTC

   Status: Identified We're investigating a bug that caused some user-specific data to be accessible to the wrong users within the same workspace from 12:07-1:10am UTC. We are reviewing impact and will communicate with affected customers, but can confirm that there was limited exposure and no cross-workspace access. As a precautionary measure we logged out all mobile sessions that were active within this time period and force reloaded all desktop and web clients. Notification emails sent during this time may contain data for other users within the same workspace. Affected components EU Region – Linear application (Degraded performance) EU Region – Linear API (Degraded performance) US Region – Linear application (Degraded performance) US Region – Linear API (Degraded performance)

2. monitoring Mar 24, 2026, 04:39 AM UTC

   Status: Monitoring Initial remediation action have been completed. Follow-up activities will continue, including assessment of impact and communication to affected customers. Affected components US Region – Linear application (Operational) US Region – Linear API (Operational) EU Region – Linear application (Operational) EU Region – Linear API (Operational)

3. monitoring Mar 24, 2026, 11:35 AM UTC

   Status: Monitoring We’ve identified an additional impact from this incident affecting some users’ inbox notifications. For impacted users, notifications were incorrectly deleted and we’re actively running a remediation job to restore those notifications now. Core product functionality has otherwise been restored, and we’ll share another update once the remediation is complete. Affected components US Region – Linear application (Degraded performance) US Region – Linear API (Operational) EU Region – Linear application (Degraded performance) EU Region – Linear API (Operational)

4. monitoring Mar 24, 2026, 01:13 PM UTC

   Status: Monitoring We’re continuing remediation work to assess the impact of user-specific data access relating to this issue. We’ll share further updates for affected workspaces as we complete the investigation and remediation steps. Separately, users experiencing problems with missing inbox notifications can find updates here: https://linearstatus.com/incidents/01KMFZGRGZ594YKSFJ2R798ZFR Affected components US Region – Linear application (Operational) US Region – Linear API (Operational) EU Region – Linear application (Operational) EU Region – Linear API (Operational)

5. monitoring Mar 24, 2026, 06:34 PM UTC

   Status: Monitoring The bug that caused data to be accessible to incorrect users within the same workspace on March 24 from 12:07-1:10am UTC was fully remediated. Follow-up activities continue, including assessment of impact and communication to affected customers. Affected components EU Region – Linear application (Operational) EU Region – Linear API (Operational) US Region – Linear application (Operational) US Region – Linear API (Operational)

6. resolved Mar 25, 2026, 11:47 PM UTC

   Status: Resolved Thank you for your patience. Affected workspaces have been notified via email. Affected components US Region – Linear application (Operational) US Region – Linear API (Operational) EU Region – Linear application (Operational) EU Region – Linear API (Operational)