Linear Outage History

Started May 12, 2026, 03:23 PM UTC· resolved May 12, 2026, 03:54 PM UTC

1. monitoring May 12, 2026, 03:23 PM UTC

   We identified elevated latency causing delays for updates in Linear. Some changes may take longer than expected to appear while services stabilize. We’re continuing to monitor recovery and will share another update once the issue is fully resolved.

2. resolved May 12, 2026, 03:54 PM UTC

   Performance has returned to normal, and updates in Linear are now processing as expected.

Read the full incident report →

Started Apr 22, 2026, 01:13 PM UTC· resolved Apr 22, 2026, 01:26 PM UTC

1. investigating Apr 22, 2026, 01:13 PM UTC

   Some users in the US may not be getting responses from the Linear agent in Slack. We are investigating and should have an update shortly

2. resolved Apr 22, 2026, 01:26 PM UTC

   We have identified and resolved the issue, this should be working correctly now for all. Thank you for your patience while we worked on this.

Read the full incident report →

Started Apr 21, 2026, 11:00 AM UTC· resolved Apr 21, 2026, 11:00 AM UTC

1. resolved Apr 21, 2026, 11:00 AM UTC

   We investigated an issue affecting events and processors in the US region, this may have cause some actions to be delayed or not triggered as expected. This has now been resolved.

Read the full incident report →

Started Apr 20, 2026, 08:18 PM UTC· resolved Apr 20, 2026, 09:58 PM UTC

1. investigating Apr 20, 2026, 08:18 PM UTC

   We're are currently investigating some delays in SLAs and Linear Agent.

2. identified Apr 20, 2026, 08:57 PM UTC

   We've identified a possible cause and are working on a fix.

3. monitoring Apr 20, 2026, 09:44 PM UTC

   We've reverted a recent change to workflow preparations. We are continuing to monitor to ensure ongoing stability.

4. resolved Apr 20, 2026, 09:58 PM UTC

   This degradation has been resolved and system performance is returning to normal. Thank you for your patience while we worked to resolve the issue.

Read the full incident report →

Started Apr 12, 2026, 10:14 AM UTC· resolved Apr 12, 2026, 10:27 AM UTC

1. investigating Apr 12, 2026, 10:14 AM UTC

   We’re investigating an issue affecting events and processors in the US East region, which may cause some actions to be delayed or not trigger as expected. We’ll continue to share updates here as we learn more.

2. resolved Apr 12, 2026, 10:27 AM UTC

   The issue affecting events and processors in the US East region has been resolved. Some events may take a short time to fully catch up, and actions may remain briefly delayed.

Read the full incident report →

Started Apr 08, 2026, 08:25 AM UTC· resolved Apr 08, 2026, 09:06 AM UTC

1. monitoring Apr 08, 2026, 08:25 AM UTC

   Some user actions may have seen processing delays, this is under control and we are monitoring.

2. resolved Apr 08, 2026, 09:06 AM UTC

   This is now resolved, the underlying root cause has been identified and fixed. Thank you for your patience.

Read the full incident report →

Started Mar 24, 2026, 03:58 PM UTC· resolved Mar 24, 2026, 08:11 PM UTC

1. investigating Mar 24, 2026, 03:58 PM UTC

   We have reports that Linear Asks are not auto-creating in some Slack channels when they are triggered via a Slack workflow. We've reproduced the issue and are investigating.

2. investigating Mar 24, 2026, 06:38 PM UTC

   We are continuing to investigate the problem with Linear Asks not auto-creating in some Slack channels when they are triggered via a Slack workflow.

3. identified Mar 24, 2026, 07:10 PM UTC

   We've identified the problem and are working on a fix.

4. resolved Mar 24, 2026, 08:11 PM UTC

   A fix has been deployed. Linear Asks are now auto-creating successfully in Slack channels when triggered via workflows.

Read the full incident report →

Started Mar 24, 2026, 01:11 PM UTC· resolved Mar 24, 2026, 03:45 PM UTC

1. identified Mar 24, 2026, 01:11 PM UTC

   We’ve identified an issue affecting user inbox notifications for a number of workspaces. Notifications were incorrectly deleted and will not appear for some users. We’re actively running a remediation task to restore those notifications now for affected users and will share updates when this job is completed.

2. resolved Mar 24, 2026, 03:45 PM UTC

   We’ve recovered the notifications that were incorrectly deleted for affected users. Inbox notifications should now be functioning normally, and we’ll continue to monitor the system to prevent recurrence.

Read the full incident report →

Started Mar 24, 2026, 04:02 AM UTC· resolved Mar 25, 2026, 11:47 PM UTC

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

   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.

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

   Initial remediation action have been completed. Follow-up activities will continue, including assessment of impact and communication to affected customers.

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

   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.

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

   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

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

   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.

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

   Thank you for your patience. Affected workspaces have been notified via email.

Read the full incident report →

Started Mar 23, 2026, 09:34 AM UTC· resolved Mar 23, 2026, 12:08 PM UTC

1. investigating Mar 23, 2026, 09:34 AM UTC

   We’re investigating reports that Linear is failing to load for some customers in Spain. Our team is actively working to identify the cause and restore normal access to all regions as quickly as possible.

2. identified Mar 23, 2026, 10:28 AM UTC

   We’ve identified the issue as a regional network problem affecting access for some users in Spain. We’re working on mitigation steps to avoid this disruption and restore normal access for all users as quickly as possible.

3. resolved Mar 23, 2026, 12:08 PM UTC

   An upstream regional networking issue impacted access for some Linear users in Spain. The issue has now been resolved, and our service is operating normally for all regions.

Read the full incident report →

Started Mar 17, 2026, 02:38 PM UTC· resolved Mar 17, 2026, 03:11 PM UTC

1. investigating Mar 17, 2026, 02:38 PM UTC

   We’re investigating reports where the Linear application is failing to load and showing a blank screen. We’re actively investigating to understand the scope of impact and identify the root cause.

2. monitoring Mar 17, 2026, 02:49 PM UTC

   The issue causing the Linear application to fail to load was due to a transient network error and has now resolved. We’re monitoring to ensure continued stability.

3. resolved Mar 17, 2026, 03:11 PM UTC

   A transient network error caused some workspaces to fail to load. This is now fully resolved.

Read the full incident report →

Started Mar 11, 2026, 11:06 AM UTC· resolved Mar 12, 2026, 01:22 PM UTC

1. monitoring Mar 11, 2026, 11:06 AM UTC

   Some GitHub pull requests in Linear may currently appear in the wrong review state (for example, PRs showing under “Needs your review” after they’ve already been reviewed or merged). We’ve identified the issue and deployed a fix. A background refresh is now running to update affected pull requests. Opening a PR in Linear should also trigger an immediate refresh for that PR. We expect review statuses to return to normal as the refresh completes over the next several hours. We’ll share another update once it’s finished.

2. resolved Mar 12, 2026, 01:22 PM UTC

   The background refresh has now completed and pull request review statuses should be displaying correctly again. If you happen to see a PR with an outdated status, navigating to the individual PR in Linear should trigger an immediate refresh. Thanks for your patience while we worked through this.

Read the full incident report →

Started Mar 09, 2026, 10:37 PM UTC· resolved Mar 09, 2026, 11:48 PM UTC

1. investigating Mar 09, 2026, 10:37 PM UTC

   We’re investigating degraded performance affecting Linear workspace creation in the US region.

2. identified Mar 09, 2026, 10:53 PM UTC

   We have identified the issue with workspace creation. The team is actively working to mitigate the problem.

3. identified Mar 09, 2026, 11:32 PM UTC

   We've identified a bug causing workspace creation requests to be incorrectly rate limited. The rate limit was being triggered by error responses, causing all new workspace creation attempts to fail for all customers. We're manually removing the rate limit keys to unblock affected customers.

4. monitoring Mar 09, 2026, 11:41 PM UTC

   Issue with creating workspaces have been mitigated. Ongoing monitoring continues to ensure all users can create new workspaces again.

5. resolved Mar 09, 2026, 11:48 PM UTC

   This incident has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue.

Read the full incident report →

Started Mar 05, 2026, 05:49 PM UTC· resolved Mar 06, 2026, 03:16 AM UTC

1. investigating Mar 05, 2026, 05:49 PM UTC

   We’re investigating degraded performance affecting Linear issue creation and linking, and prompts to the Linear agent in Slack, in the US region. This impacts Linear issue creation or linking requests coming from integrations (such as Intercom and Zendesk), form templates, and general prompts to the Linear agent for Slack. Our team is actively investigating the root cause. We’ll continue to provide updates on this status page as we learn more.

2. investigating Mar 05, 2026, 07:15 PM UTC

   We’re seeing improvements in latency for actions taken within Linear or when creating and updating issues through integrations, and are continuing to monitor for any remaining performance degradation. Separately, we’re investigating reports of the Linear agent in Slack failing to respond to prompts. Our team is working to identify the root cause and will continue to provide updates here as we learn more.

3. identified Mar 05, 2026, 07:39 PM UTC

   All Linear operations have returned to normal outside of the Linear agent for Slack. We’ve identified the issue causing failures or delays with the Linear agent and are continuing to monitor for resolution. We’ll share updates as we learn more.

4. monitoring Mar 05, 2026, 08:56 PM UTC

   Earlier today, incidents affecting external services that Linear integrates with resulted in a surge of retried and delayed events being processed by our systems. This temporarily increased system load and created a backlog of background tasks. While we worked through this backlog, some asynchronous updates in Linear—such as integration activity, the Linear agent in Slack and other background updates—appeared delayed. Our systems are actively processing queued tasks, and we're seeing stabilization. We'll continue to monitor for full resolution.

5. monitoring Mar 05, 2026, 09:40 PM UTC

   As we continue processing a surge of background tasks following disruptions involving external services that Linear integrates with, some asynchronous updates in Linear—such as integration activity and the Linear agent in Slack—may experience delays. Our systems are actively processing queued tasks and we’re monitoring for full recovery.

6. monitoring Mar 06, 2026, 12:21 AM UTC

   Though we’re continuing to observe some persistent latency, system performance is improving as our systems recover from the earlier surge in background task processing. Some asynchronous updates in Linear—such as integration activity and the Linear agent in Slack—may still experience slight delays. We’re continuing to monitor performance closely.

7. monitoring Mar 06, 2026, 02:35 AM UTC

   We are continuing to process background jobs generated by incidents affecting external integrations. Some customers may still experience latency. We’re continuing to monitor performance as systems stabilize.

8. resolved Mar 06, 2026, 03:16 AM UTC

   All background jobs generated by earlier incidents affecting external integrations have now been processed, and system performance has returned to normal. If you’re still experiencing any problems, please reach out to [email protected]. Thank you for your patience while we worked to resolve this.

Read the full incident report →

Started Mar 05, 2026, 09:30 AM UTC· resolved Mar 05, 2026, 09:46 AM UTC

1. investigating Mar 05, 2026, 09:30 AM UTC

   We're investigating issues with projects not appearing in views. Projects will be findable through the issues page in the meantime. We'll update our status with news as soon as we have fixed the problem.

2. investigating Mar 05, 2026, 09:43 AM UTC

   We've released a fix for the project and labels so they will reappear. You may need to refresh your client (CMD+R on Mac / CTRL+R on Windows)

3. resolved Mar 05, 2026, 09:46 AM UTC

   Normal service has been restored.

Read the full incident report →

Started Mar 04, 2026, 06:59 PM UTC· resolved Mar 04, 2026, 08:16 PM UTC

1. investigating Mar 04, 2026, 06:59 PM UTC

   We’re investigating degraded performance with processing requests with Slack integrations in the US East region. This affects Asks, the Linear agent in Slack, and our standard Slack integration. Creating and linking issues may be delayed. We’ll keep our status site updated as we investigate and scale up our services.

2. monitoring Mar 04, 2026, 07:45 PM UTC

   We’ve identified an unexpected increase in system load that caused delays in Slack integration processing in the US East region. Services have recovered after scaling up our systems. We are continuing to monitor to ensure ongoing stability.

3. resolved Mar 04, 2026, 08:16 PM UTC

   This degradation has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue.

Read the full incident report →

Started Mar 02, 2026, 05:28 PM UTC· resolved Mar 02, 2026, 09:02 PM UTC

1. identified Mar 02, 2026, 05:28 PM UTC

   We’ve identified a bug that caused a subset of agent users (including Cursor, GitHub Copilot, and Codex) to become unintentionally suspended. Our team has implemented a fix and deployment is currently underway. We expect affected agent access to be restored shortly. We’ll provide another update once the rollout is complete.

2. identified Mar 02, 2026, 05:37 PM UTC

   Affected agents are now active again in the EU region. US region to follow shortly.

3. resolved Mar 02, 2026, 05:40 PM UTC

   Affected agents in all regions are now active again. Normal functionality has been restored.

4. identified Mar 02, 2026, 06:23 PM UTC

   Following our earlier update, we’re investigating reports that a small number of users are continuing to see Cursor, GitHub Copilot, and Codex agents in a suspended state. Our team is actively working to ensure full restoration of access. We’ll continue to provide updates here as we learn more.

5. resolved Mar 02, 2026, 09:02 PM UTC

   Any remaining affected agents are now active again in all regions. Access has been fully restored. If you continue to see Cursor, GitHub Copilot, and Codex agents in a suspended state unexpectedly, please reach out to [email protected].

Read the full incident report →

Started Feb 09, 2026, 05:41 PM UTC· resolved Feb 09, 2026, 09:15 PM UTC

1. identified Feb 09, 2026, 05:41 PM UTC

   We’re investigating degraded performance with processing requests with Slack integrations in the US East region. Creating and linking issues may be delayed. We’ll keep our status site updated as we investigate and scale up our services.

2. monitoring Feb 09, 2026, 06:37 PM UTC

   We’ve identified the cause of degraded performance affecting Slack integrations in the US East region. As our systems continue to stabilize, some users may continue to see minor latency when creating or linking issues through Slack. We’re monitoring closely and will update once the latency resolves fully.

3. resolved Feb 09, 2026, 09:15 PM UTC

   Earlier today, some users experienced errors and increased latency when creating and updating Linear issues from Slack. This was caused by internal changes to our notification processing that didn’t scale as expected, leading to processing backlogs in some cases. The degradation has been resolved, and Slack-based issue actions are now operating normally. We’ve stabilized our infrastructure and are adjusting our approach to prevent similar surges going forward. Thanks for your patience while we worked through this.

Read the full incident report →

Started Jan 27, 2026, 02:55 PM UTC· resolved Jan 27, 2026, 02:55 PM UTC

1. resolved Jan 27, 2026, 02:55 PM UTC

   Earlier today, some users may have encountered errors when creating Linear issues from Slack using the Linear or Linear Asks integration. The issue has been fully resolved, and all Slack-based issue creation is now operating normally. We apologize for any disruption this caused, and thank you for your patience.

Read the full incident report →

Started Jan 17, 2026, 10:00 AM UTC· resolved Jan 17, 2026, 10:00 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 28, 2025, 09:39 PM UTC· resolved Dec 28, 2025, 09:39 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 05, 2025, 08:56 AM UTC· resolved Dec 05, 2025, 09:32 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 03, 2025, 06:13 PM UTC· resolved Dec 03, 2025, 06:41 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 03, 2025, 02:01 PM UTC· resolved Dec 03, 2025, 03:03 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 21, 2025, 03:23 PM UTC· resolved Nov 21, 2025, 06:20 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →