Linear Outage History

Linear experienced a 1.2-hour service incident where workspace creation failed for all customers in the US region due to a bug that incorrectly triggered rate limiting on error responses. The team identified that workspace creation requests were being blocked by rate limits that were erroneously activated by failed attempts, creating a cascading failure. The issue was resolved by manually removing the problematic rate limit keys, restoring workspace creation functionality for all users.

Linear experienced degraded performance in the US region affecting issue creation and linking from integrations (Intercom, Zendesk), form templates, and the Linear agent in Slack due to a surge of background tasks caused by incidents with external services. The backlog of retried and delayed events temporarily increased system load, causing delays in asynchronous updates and integration activity. The incident was resolved by processing the queued background tasks, with systems gradually stabilizing and returning to normal performance over the 9.5-hour duration.

Linear experienced a 20-minute incident where projects were not appearing in views, though they remained accessible through the issues page. The engineering team released a fix that restored project and label visibility, requiring users to refresh their clients to see the changes.

Linear experienced degraded performance with Slack integrations in the US East region, causing delays in creating and linking issues through Asks, the Linear agent in Slack, and the standard Slack integration. The issue was caused by an unexpected increase in system load and lasted 1.4 hours. The service was restored after scaling up systems, with continued monitoring for stability.

A bug in Linear caused a subset of agent app users, including those using Cursor, GitHub Copilot, and Codex, to become unintentionally suspended and lose access to the service. Linear's team identified the issue, implemented a fix, and deployed it to restore agent access. The incident lasted 13 minutes with affected users experiencing temporary service disruption until the rollout was completed.