Linear

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-27 10:56 UTC

   We are investigating an outage with our EU server. We'll post updates here as soon as possible.

2. monitoring 2026-09-27 11:15 UTC

   We've identified a faulty deployment and a restart has reenabled connections. EU users should be able to access Linear now and changes offline should now be synced. Please reach out to support@linear.app if you are experiencing issues. Given the scope and impact of the incident,...

3. resolved 2026-09-27 12:02 UTC

   The issues affecting EU Linear users from 00:55 to 11:15 UTC today have been resolved and changes made offline should now be synced. Please reach out to [support@linear.app](mailto:support@linear.app) if you are experiencing issues. We apologize for the downtime and are...

4. resolved 2026-10-01 17:50 UTC

   We've published a post mortem with details on this incident including a timeline of events and prevention steps for the future:

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-05 15:17 UTC

   Linear's services(in particular the API and MCP server) are currently impacted for some users hosted in the US region. Our team is investigating and will provide an update shortly.

2. monitoring 2026-09-05 15:33 UTC

   Normal levels of operation have resumed, we'll continue to monitor the situation before marking fully resolved.

3. resolved 2026-09-05 16:13 UTC

   Normal levels of operation has been fully restored. Incident is now resolved and closed.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-09-01 10:27 UTC

   We're aware of upstream issues which may cause increased delays or failed delivery of Android push notifications primarily in the US region. We will continue to monitor the upstream providers status and keep our status site updated accordingly.

2. resolved 2026-09-01 12:23 UTC

   Normal functionality has resumed.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-19 15:26 UTC

   Some customers may experience delayed responses from Linear agent and delayed runs for automated actions through Loops. We're investigating this issue now and will share an update as soon as possible.

2. resolved 2026-08-19 15:42 UTC

   Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-12 16:01 UTC

   Linear docs are currently unable to load, we are making a change to fix this as soon as possible.

2. resolved 2026-08-12 16:03 UTC

   Documentation site now loads after refreshing.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: OpenAI.

1. investigating 2026-08-10 03:54 UTC

   Some users are unable to start Codex sessions from Linear. We’re investigating and working with the integration provider to resolve the issue.

2. investigating 2026-08-13 20:39 UTC

   The Codex integration remains unavailable for affected users due to an underlying delivery issue. We are continuing to work with OpenAI, who has confirmed its teams are investigating."

3. resolved 2026-08-14 18:21 UTC

   The connection between Linear and OpenAI was failing and has now been rectified.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-16 16:47 UTC

   Some customers are experiencing issues with Linear loading. We are investigating - apologies for the inconvenience.

2. investigating 2026-07-16 17:15 UTC

   Some customers in the US region are still experiencing issues with Linear loading. We have rolled back a recent change and are continuing to mitigate the issue, but some affected users may still see problems. We’ll share another update shortly.

3. monitoring 2026-07-16 18:09 UTC

   We are seeing improvements after updates and are continuing to monitor for stability.

4. resolved 2026-07-16 18:20 UTC

   Recent feature roll-outs added extra load to our databases, and a fix has been implemented. Thank you for your patience while we worked to resolve this.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-30 20:12 UTC

   Some users in India may be experiencing difficulties loading Linear in the web and desktop apps. We are investigating the issue and working to mitigate it.

2. identified 2026-06-30 20:35 UTC

   We identified regional networking issues from an upstream provider affecting some users in India, which may prevent Linear from loading. We’re continuing to monitor the situation and will share further updates as we learn more.

3. resolved 2026-06-30 21:44 UTC

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

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-22 15:27 UTC

   We have had reports of Linear not loading for some users. We are investigating and will be back with further updates as soon as possible.

2. investigating 2026-06-22 16:09 UTC

   We are continuing to investigate to narrow down the root cause. We apologise for the inconvenience this is causing, thank you for your continued patience.

3. investigating 2026-06-22 17:04 UTC

   Our team is still actively investigating. We'll provide a further update by 17:45 UTC - thank you for your continued patience.

4. monitoring 2026-06-22 17:46 UTC

   We are seeing improvements after updates, and users are now able to load and sync in Linear again. We are continuing to monitor improvements.

5. resolved 2026-06-22 18:15 UTC

   Some customers were experiencing issues with Linear loading and syncing. Performance has returned to normal, and the issue is resolved. We appreciate your patience while we worked on this.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-22 10:27 UTC

   Some users with EU-hosted workspaces may be experiencing delays syncing changes. Service is recovering, and we are monitoring performance.

2. resolved 2026-06-22 11:00 UTC

   Some users with EU-hosted workspaces experienced delays syncing changes for a short period of time this morning. Sync performance has returned to normal, and the issue is resolved. Thank you for your patience while we worked on this.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-17 22:52 UTC

   We're investigating reports of general latency when taking actions in Linear — we're working to confirm the suspected root cause and remediate the degradation. We'll provide updates as we have them.

2. monitoring 2026-06-17 23:08 UTC

   We’ve rolled back a recent change that may have contributed to the slowdown and performance is improving. We’re keeping a close eye on continued recovery.

3. resolved 2026-06-17 23:17 UTC

   The increased latency has been resolved, and Linear should be operating normally again. We rolled back the query change that caused the slowdown and have confirmed performance has recovered.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-17 17:05 UTC

   Some users may be experiencing errors when loading code diffs in Linear. We are investigating and will share an update as soon as we have more information.

2. monitoring 2026-06-17 17:39 UTC

   We identified the cause of errors when navigating to _Reviews_ and reverted the impacting change. Reported errors are stabilizing, and affected users should see recovery after refreshing Linear. We are monitoring to ensure continued stability.

3. monitoring 2026-06-17 18:10 UTC

   The revert resolved broader errors affecting navigation to the Reviews tab. However, a smaller subset of errors continues when opening specific pull requests. We are investigating these remaining cases and monitoring recovery as we work toward full resolution.

4. monitoring 2026-06-17 18:33 UTC

   We identified and addressed the remaining cause of errors affecting specific pull requests. The Reviews experience is now functioning normally, and any remaining affected users should see recovery after refreshing Linear. We’re monitoring for continued stability before fully...

5. resolved 2026-06-17 20:04 UTC

   This issue has been resolved, and the Reviews experience is functioning normally — thank you for your patience. If you continue to see any trouble, please reach out to support@linear.app and we'll take a look!

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-16 15:05 UTC

   Some users may be experiencing delays when using automations, including the Linear Agent and Asks. We are investigating and will provide updates as more information becomes available.

2. investigating 2026-06-16 16:07 UTC

   Some users in our US and European regions continue to experience delayed responses from Linear Agent and some other automations including Asks. We have increased service capacity and are continuing to work towards restoring normal response times.

3. monitoring 2026-06-16 17:47 UTC

   Agent responses and other delayed workflows should now be operating normally. We’re continuing to monitor performance to ensure recovery remains stable.

4. monitoring 2026-06-16 19:39 UTC

   Processing continues to operate normally, and we have not observed further errors. We’re continuing to monitor performance to ensure the recovery remains stable.

5. resolved 2026-06-16 21:55 UTC

   The delays affecting agent responses and other workflows have been resolved. We're sorry for the disruption.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-15 10:58 UTC

   We're investigating a problem with the right-click/context menu on issues. Command menu or keyboard shortcuts are functional as a workaround in the meantime. We'll keep our status site updated with news as we work towards a fix.

2. resolved 2026-06-15 11:03 UTC

   We've identified the problem and deployed a fix. You may need to refresh (⌘+R / CTRL+R) to get the latest changes.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-09 17:08 UTC

   Linear is currently unavailable for many users across the web and desktop apps. We are investigating a partial outage, and will post an update shortly.

2. monitoring 2026-06-09 17:20 UTC

   Linear should now be available again. We’re monitoring recovery to ensure service remains stable.

3. resolved 2026-06-09 17:48 UTC

   This incident has been resolved, and Linear is operating normally across all regions. We rolled back the affected services and have confirmed that error rates remain normal. We apologize for the disruption.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 12:49 UTC

   We’re currently investigating an issue affecting the in-app contact form. In the meantime, if you need to reach our support team, please contact us directly at [support@linear.app](mailto:support@linear.app "support@linear.app"). We’ll share another update as soon as we have...

2. investigating 2026-06-04 13:20 UTC

   The problem with in-app submissions is still being worked on, we've isolated the problem and it should be restored soon.

3. monitoring 2026-06-04 14:23 UTC

   We've confirmed that new submissions through our in-app contact form are being received successfully again. We're continuing to process and review messages that were impacted and will follow up with affected customers as quickly as possible. Thank you for your patience while we...

4. resolved 2026-06-04 15:09 UTC

   We've resolved the issue affecting submissions through our in-app contact form, and new support requests are being received successfully again. Our team will continue reviewing and replying to delayed support requests as quickly as possible. We apologize for the delay and...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-03 14:07 UTC

   Due to an upstream provider outage, code intelligence requests through the Linear Agent are currently failing to process. We'll continue to observe the situation and once the upstream issue is resolved we'll resolve our status.

2. resolved 2026-06-03 14:19 UTC

   Normal functionality has resumed to the Linear Agent's coding intelligence features.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-31 18:49 UTC

   We’re investigating delays affecting event processing for some workspaces hosted in our US region. This may cause updates in Linear to appear delayed or out of date. We’re actively working on a fix and will share another update as soon as we have more information.

2. monitoring 2026-05-31 19:36 UTC

   We’ve implemented a fix for delays affecting updates for some workspaces hosted in our US region, and processing has resumed. Some users may still see delayed or out-of-date information while the remaining backlog clears. We’re continuing to monitor recovery closely.

3. resolved 2026-05-31 20:03 UTC

   We’ve resolved the delays that were affecting updates for some workspaces hosted in our US region, and service should now be operating normally. We hit an unexpected condition in our event processing that caused the system to back up. If you still see stale information in...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 14:25 UTC

   We’re investigating an issue causing Linear to fail to load for some users. You may see a network error while opening the app while this is ongoing. We’re working on mitigation and will share another update as soon as we have more information.

2. investigating 2026-05-28 14:55 UTC

   We’re continuing to investigate an issue causing Linear to fail to load for some users. You may see a network error when opening the app while this incident is ongoing. We will share another update as soon as we have more information and we're sorry for the difficulty in the...

3. resolved 2026-05-28 15:22 UTC

   This incident has now been resolved and Linear should now be loading normally again for all users. We identified an error with DDOS protection rules being applied in error, and applied mitigation changes to prevent this from affecting user logins. If you still run into problems...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 13:45 UTC

   We’re investigating an issue causing email intake for Linear Asks to fail. Emails sent to intake addresses may bounce, and new issues may not be created from Asks intake emails while we work on mitigation. We’ll share another update as soon as we have more information.

2. identified 2026-05-28 14:08 UTC

   We’re continuing to investigate an issue affecting Linear Asks email intake. Emails sent to intake addresses may bounce, and new asks will not be created from email while this is ongoing. We are working to restore email intake functionality and will continue share updates as...

3. resolved 2026-05-28 14:17 UTC

   Asks email intake has been restored and is working again. We identified the issue and implemented a fix, and have confirmed the flow is working again end to end. Please reach out to support@linear.app if you experience any problems with email intake after this time.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-25 13:11 UTC

   Task processing in our EU region was briefly delayed from 12:45 to 13:05 UTC after capacity scaled down too far, which slowed some background actions from completing normally. We scaled capacity back up and processing has recovered. Service should now be operating normally.

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-05-22 08:22 UTC

   Earlier today, some US customers may have seen degraded or incomplete search results for a number of hours. This issue has now been resolved, and search should be working normally again. The impact was caused by backed-up event processing, which has since been cleared. We’re...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-19 04:02 UTC

   We’re investigating delays in background processing. This may affect things like notifications, emails, webhooks, automations, and some integrations. We’re working to identify the cause and mitigate the issue, though are seeing early signs of stabilization.

2. monitoring 2026-05-19 04:11 UTC

   We identified failures with our event processing and our backlog of events has returned to regular levels and delays are no longer significant. We're continuing to monitor for stability.

3. resolved 2026-05-19 04:56 UTC

   We mitigated the issue causing delays in background event processing, and the backlog has returned to regular levels. Systems are operating normally — you should no longer experience issues with notification or email delivery, webhooks, or other event-driven updates. Please...

4. monitoring 2026-05-19 10:59 UTC

   We've monitoring further delays in background activity that have affected some users in recent days. While most of the service is operating normally, some notifications and updates may still be delayed as recovery continues for affected users. We’re seeing improvement and will...

5. monitoring 2026-05-19 12:25 UTC

   We're continuing to work through a backlog of delayed background activity affecting some users. This includes delays to email and Slack notifications as well as webhooks. We've scaled up our infrastructure to process the backlog more quickly and are actively monitoring progress....

6. monitoring 2026-05-19 20:34 UTC

   We’ve identified the cause of the delays affecting background activity for some users, including notifications, webhooks, and other asynchronous updates. We’re actively applying remediation to reduce pressure on our task processing system and restore normal performance. We’ll...

7. monitoring 2026-05-20 00:10 UTC

   We’ve addressed the issue that was causing delays in background task processing earlier today, and task activity has been operating normally again for the past few hours. A remaining search indexing backlog means some recent changes may still take a few more hours to appear in...

8. resolved 2026-05-20 06:13 UTC

   We’ve resolved the issue that caused delays in background task processing and search indexing. Systems are now operating normally again. Recent changes should appear as expected in search, and you should no longer experience delays with notifications, webhooks, automations, or...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-18 21:43 UTC

   From approximately 21:15 to 21:20 UTC, customers using cycles may have seen errors in Linear. This was caused by unintended side effects from an internal migration related to ongoing performance and technical-debt improvements. Our team identified the issue quickly, rolled back...

2. resolved 2026-05-18 21:57 UTC

   As noted, an internal migration related to ongoing performance and tech-debt improvements caused errors affecting customers using cycles. Our team identified and reverted the issue quickly, and service has now fully recovered. We appreciate your patience as we worked to resolve...

Excerpts are shortened. Read the full incident on Linear's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-05-14 14:51 UTC

   We’re investigating an incident affecting Linear Asks, Slack, and Slack agent functionality due to an upstream provider issue. Some Slack-related workflows may be delayed or unavailable. We're monitoring the situation and will share updates as soon as possible.

2. identified 2026-05-14 15:33 UTC

   We’re still investigating an incident affecting Linear Asks, Slack, and Slack agent functionality due to an upstream provider issue. Some Slack-related workflows may be delayed or unavailable while this is ongoing. We’ll share an update as soon as the upstream issue is resolved...

3. resolved 2026-05-14 15:57 UTC

   This incident has been resolved. Linear Asks, Slack, and Slack agent functionality should now be operating normally after the upstream provider issue was fixed.

Excerpts are shortened. Read the full incident on Linear's status page.