Linear Outage History

Linear is up right now

Linear had 43 outages in the last 2 years totaling 10h 52m of downtime — averaging 1.8 incidents per month.

There were 43 Linear outages since November 18, 2025 totaling 10h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://linearstatus.com

Minor March 17, 2026

Linear client failing to load

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
  1. 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.

  2. 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)

  3. 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 →

Minor March 12, 2026

GitHub Pull Request review status may appear incorrect

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
  1. 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)

  2. 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 →

Minor March 9, 2026

Errors in creating workspaces

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
  1. 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)

  2. 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)

  3. 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)

  4. 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)

  5. 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 →

Minor March 5, 2026

Projects missing from views

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
  1. 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)

  2. 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)

  3. 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 →

Minor March 4, 2026

Delays creating or updating Linear issues through Slack

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
  1. 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)

  2. 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)

  3. 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 →

Minor March 2, 2026

Subset of agent app users experiencing access problems

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
  1. 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)

  2. 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)

  3. 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)

  4. 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)

  5. 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 →

Minor February 9, 2026

Delays creating and linking issues from Slack

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
  1. 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)

  2. 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)

  3. 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 →