- Detected by Pingoru
- Apr 22, 2026, 01:26 PM UTC
- Resolved
- Apr 22, 2026, 01:26 PM UTC
- Duration
- —
Affected: US Region – Integrations
Timeline · 2 updates
-
investigating Apr 22, 2026, 01:13 PM UTC
Status: Investigating 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 Affected components US Region – Integrations (Degraded performance)
-
resolved Apr 22, 2026, 01:26 PM UTC
Status: Resolved 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. Affected components US Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 01:34 PM UTC
- Resolved
- Apr 21, 2026, 11:00 AM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 09:58 PM UTC
- Resolved
- Apr 20, 2026, 09:58 PM UTC
- Duration
- —
Affected: US Region – Linear application
Timeline · 4 updates
-
investigating Apr 20, 2026, 08:18 PM UTC
Status: Investigating We're are currently investigating some delays in SLAs and Linear Agent. Affected components US Region – Linear application (Partial outage)
-
identified Apr 20, 2026, 08:57 PM UTC
Status: Identified We've identified a possible cause and are working on a fix. Affected components US Region – Linear application (Partial outage)
-
monitoring Apr 20, 2026, 09:44 PM UTC
Status: Monitoring We've reverted a recent change to workflow preparations. We are continuing to monitor to ensure ongoing stability. Affected components US Region – Linear application (Operational)
-
resolved Apr 20, 2026, 09:58 PM UTC
Status: Resolved This degradation has been resolved and system performance is returning to normal. Thank you for your patience while we worked to resolve the issue. Affected components US Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 10:27 AM UTC
- Resolved
- Apr 12, 2026, 10:27 AM UTC
- Duration
- —
Affected: US Region – Linear APIUS Region – Linear applicationUS Region – Integrations
Timeline · 2 updates
-
investigating Apr 12, 2026, 10:14 AM UTC
Status: Investigating 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. Affected components US Region – Linear application (Degraded performance) US Region – Linear API (Degraded performance) US Region – Integrations (Degraded performance)
-
resolved Apr 12, 2026, 10:27 AM UTC
Status: Resolved 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. Affected components US Region – Integrations (Operational) US Region – Linear application (Operational) US Region – Linear API (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 09:06 AM UTC
- Resolved
- Apr 08, 2026, 09:06 AM UTC
- Duration
- —
Affected: US Region – Linear APIUS Region – Linear applicationUS Region – Integrations
Timeline · 2 updates
-
monitoring Apr 08, 2026, 08:25 AM UTC
Status: Monitoring Some user actions may have seen processing delays, this is under control and we are monitoring. Affected components US Region – Integrations (Degraded performance) US Region – Linear application (Degraded performance) US Region – Linear API (Degraded performance)
-
resolved Apr 08, 2026, 09:06 AM UTC
Status: Resolved This is now resolved, the underlying root cause has been identified and fixed. Thank you for your patience. Affected components US Region – Linear application (Operational) US Region – Linear API (Operational) US Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 11:47 PM UTC
- Resolved
- Mar 25, 2026, 11:47 PM UTC
- Duration
- —
Affected: EU Region – Linear APIUS Region – Linear APIEU Region – Linear applicationUS Region – Linear application
Timeline · 6 updates
-
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)
-
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)
-
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)
-
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)
-
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)
-
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)
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 08:11 PM UTC
- Resolved
- Mar 24, 2026, 08:11 PM UTC
- Duration
- —
Affected: EU Region – IntegrationsUS Region – Integrations
Timeline · 4 updates
-
investigating Mar 24, 2026, 03:58 PM UTC
Status: Investigating 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. Affected components US Region – Integrations (Degraded performance) EU Region – Integrations (Degraded performance)
-
investigating Mar 24, 2026, 06:38 PM UTC
Status: Investigating 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. Affected components EU Region – Integrations (Degraded performance) US Region – Integrations (Degraded performance)
-
identified Mar 24, 2026, 07:10 PM UTC
Status: Identified We've identified the problem and are working on a fix. Affected components EU Region – Integrations (Degraded performance) US Region – Integrations (Degraded performance)
-
resolved Mar 24, 2026, 08:11 PM UTC
Status: Resolved A fix has been deployed. Linear Asks are now auto-creating successfully in Slack channels when triggered via workflows. Affected components US Region – Integrations (Operational) EU Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 03:45 PM UTC
- Resolved
- Mar 24, 2026, 03:45 PM UTC
- Duration
- —
Affected: EU Region – Linear applicationUS Region – Linear application
Timeline · 2 updates
-
identified Mar 24, 2026, 01:11 PM UTC
Status: Identified 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. Affected components EU Region – Linear application (Partial outage) US Region – Linear application (Partial outage)
-
resolved Mar 24, 2026, 03:45 PM UTC
Status: Resolved 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. Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 23, 2026, 12:08 PM UTC
- Resolved
- Mar 23, 2026, 12:08 PM UTC
- Duration
- —
Affected: EU Region – Linear applicationUS Region – Linear application
Timeline · 3 updates
-
investigating Mar 23, 2026, 09:34 AM UTC
Status: Investigating 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. Affected components EU Region – Linear application (Partial outage) US Region – Linear application (Partial outage)
-
identified Mar 23, 2026, 10:28 AM UTC
Status: Identified 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. Affected components US Region – Linear application (Partial outage) EU Region – Linear application (Partial outage)
-
resolved Mar 23, 2026, 12:08 PM UTC
Status: Resolved 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. Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 03:11 PM UTC
- Resolved
- Mar 17, 2026, 03:11 PM UTC
- Duration
- —
Affected: EU Region – Linear applicationUS Region – Linear application
Timeline · 3 updates
-
investigating Mar 17, 2026, 02:38 PM UTC
Status: Investigating 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.
-
monitoring Mar 17, 2026, 02:49 PM UTC
Status: Monitoring 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. Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
-
resolved Mar 17, 2026, 03:11 PM UTC
Status: Resolved A transient network error caused some workspaces to fail to load. This is now fully resolved. Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 01:22 PM UTC
- Resolved
- Mar 12, 2026, 01:22 PM UTC
- Duration
- —
Affected: EU Region – Linear APIUS Region – Linear APIEU Region – IntegrationsUS Region – Integrations
Timeline · 2 updates
-
monitoring Mar 11, 2026, 11:06 AM UTC
Status: Monitoring 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. Affected components US Region – Linear API (Degraded performance) US Region – Integrations (Degraded performance) EU Region – Integrations (Degraded performance) EU Region – Linear API (Degraded performance)
-
resolved Mar 12, 2026, 01:22 PM UTC
Status: Resolved 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. Affected components EU Region – Linear API (Operational) US Region – Linear API (Operational) US Region – Integrations (Operational) EU Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 09, 2026, 11:48 PM UTC
- Resolved
- Mar 09, 2026, 11:48 PM UTC
- Duration
- —
Affected: US Region – Linear application
Timeline · 5 updates
-
investigating Mar 09, 2026, 10:37 PM UTC
Status: Investigating We’re investigating degraded performance affecting Linear workspace creation in the US region. Affected components US Region – Linear application (Degraded performance)
-
identified Mar 09, 2026, 10:53 PM UTC
Status: Identified We have identified the issue with workspace creation. The team is actively working to mitigate the problem. Affected components US Region – Linear application (Partial outage)
-
identified Mar 09, 2026, 11:32 PM UTC
Status: Identified 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. Affected components US Region – Linear application (Partial outage)
-
monitoring Mar 09, 2026, 11:41 PM UTC
Status: Monitoring Issue with creating workspaces have been mitigated. Ongoing monitoring continues to ensure all users can create new workspaces again. Affected components US Region – Linear application (Degraded performance)
-
resolved Mar 09, 2026, 11:48 PM UTC
Status: Resolved This incident has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue. Affected components US Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 03:16 AM UTC
- Resolved
- Mar 06, 2026, 03:16 AM UTC
- Duration
- —
Affected: US Region – Linear applicationUS Region – Integrations
Timeline · 8 updates
-
investigating Mar 05, 2026, 05:49 PM UTC
Status: Investigating 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. Affected components US Region – Integrations (Degraded performance)
-
investigating Mar 05, 2026, 07:15 PM UTC
Status: Investigating 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. Affected components US Region – Linear application (Degraded performance) US Region – Integrations (Degraded performance)
-
identified Mar 05, 2026, 07:39 PM UTC
Status: Identified 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. Affected components US Region – Integrations (Degraded performance) US Region – Linear application (Operational)
-
monitoring Mar 05, 2026, 08:56 PM UTC
Status: Monitoring 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. Affected components US Region – Linear application (Operational) US Region – Integrations (Degraded performance)
-
monitoring Mar 05, 2026, 09:40 PM UTC
Status: Monitoring 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. Affected components US Region – Linear application (Operational) US Region – Integrations (Degraded performance)
-
monitoring Mar 06, 2026, 12:21 AM UTC
Status: Monitoring 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. Affected components US Region – Integrations (Degraded performance) US Region – Linear application (Operational)
-
monitoring Mar 06, 2026, 02:35 AM UTC
Status: Monitoring 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. Affected components US Region – Linear application (Degraded performance) US Region – Integrations (Degraded performance)
-
resolved Mar 06, 2026, 03:16 AM UTC
Status: Resolved 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. Affected components US Region – Linear application (Operational) US Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 05, 2026, 09:46 AM UTC
- Resolved
- Mar 05, 2026, 09:46 AM UTC
- Duration
- —
Affected: EU Region – Linear applicationUS Region – Linear application
Timeline · 3 updates
-
investigating Mar 05, 2026, 09:30 AM UTC
Status: Investigating 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. Affected components US Region – Linear application (Degraded performance) EU Region – Linear application (Degraded performance)
-
investigating Mar 05, 2026, 09:43 AM UTC
Status: Investigating 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) Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
-
resolved Mar 05, 2026, 09:46 AM UTC
Status: Resolved Normal service has been restored. Affected components US Region – Linear application (Operational) EU Region – Linear application (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 08:16 PM UTC
- Resolved
- Mar 04, 2026, 08:16 PM UTC
- Duration
- —
Affected: US Region – Integrations
Timeline · 3 updates
-
investigating Mar 04, 2026, 06:59 PM UTC
Status: Investigating 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. Affected components US Region – Integrations (Degraded performance)
-
monitoring Mar 04, 2026, 07:45 PM UTC
Status: Monitoring 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. Affected components US Region – Integrations (Degraded performance)
-
resolved Mar 04, 2026, 08:16 PM UTC
Status: Resolved This degradation has been resolved and system performance has returned to normal. Thank you for your patience while we worked to resolve the issue. Affected components US Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 09:02 PM UTC
- Resolved
- Mar 02, 2026, 09:02 PM UTC
- Duration
- —
Affected: EU Region – IntegrationsUS Region – Integrations
Timeline · 5 updates
-
identified Mar 02, 2026, 05:28 PM UTC
Status: Identified 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. Affected components US Region – Integrations (Partial outage) EU Region – Integrations (Partial outage)
-
identified Mar 02, 2026, 05:37 PM UTC
Status: Identified Affected agents are now active again in the EU region. US region to follow shortly. Affected components US Region – Integrations (Partial outage) EU Region – Integrations (Operational)
-
resolved Mar 02, 2026, 05:40 PM UTC
Status: Resolved Affected agents in all regions are now active again. Normal functionality has been restored. Affected components US Region – Integrations (Operational) EU Region – Integrations (Operational)
-
identified Mar 02, 2026, 06:23 PM UTC
Status: Identified 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. Affected components US Region – Integrations (Partial outage) EU Region – Integrations (Partial outage)
-
resolved Mar 02, 2026, 09:02 PM UTC
Status: Resolved 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]. Affected components US Region – Integrations (Operational) EU Region – Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 09:15 PM UTC
- Resolved
- Feb 09, 2026, 09:15 PM UTC
- Duration
- —
Affected: US Region – Integrations
Timeline · 3 updates
-
identified Feb 09, 2026, 05:41 PM UTC
Status: Identified 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. Affected components US Region – Integrations (Degraded performance)
-
monitoring Feb 09, 2026, 06:37 PM UTC
Status: Monitoring 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. Affected components US Region – Integrations (Degraded performance)
-
resolved Feb 09, 2026, 09:15 PM UTC
Status: Resolved 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. Affected components US Region – Integrations (Operational)
Read the full incident report →