https://linearstatus.com/ Linear status 2026-03-16T23:52:02.946Z incident.io Linear status page updates https://storage.googleapis.com/incident-io-status-page-logos/01F3XM6VBTA29DFRAPT6VQZZ6K/linear/vvd2ez05.png <![CDATA[GitHub Pull Request review status may appear incorrect]]> https://linearstatus.com//incidents/01KKE983BSMR04B1F4EK2RSAFK 2026-03-12T13:22:57.096Z 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
  • US Region – Integrations (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear API (Operational)
]]>
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
  • US Region – Integrations (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear API (Operational)
]]>
<![CDATA[Errors in creating workspaces]]> https://linearstatus.com//incidents/01KKABZSYJW4WDBF29BKMJE7C5 2026-03-09T23:48:57.868Z 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)
]]>
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)
]]>
<![CDATA[Delays in updates from integrations and other background activity]]> https://linearstatus.com//incidents/01KJZHWXQNB5THZFRCCREFMQE5 2026-03-06T03:16:27.126Z 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)
]]>
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)
]]>
<![CDATA[Projects missing from views]]> https://linearstatus.com//incidents/01KJYNBFA2WG2GS444RCR22T5X 2026-03-05T09:46:56.581Z Status: Resolved

Normal service has been restored.

Affected components
  • EU Region – Linear application (Operational)
  • US Region – Linear application (Operational)
]]>
Status: Resolved

Normal service has been restored.

Affected components
  • EU Region – Linear application (Operational)
  • US Region – Linear application (Operational)
]]>
<![CDATA[Delays creating or updating Linear issues through Slack]]> https://linearstatus.com//incidents/01KJX3FWW7D7F9SCJ829S6CZVT 2026-03-04T20:16:33.114Z 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)
]]>
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)
]]>
<![CDATA[Subset of agent app users experiencing access problems]]> https://linearstatus.com//incidents/01KJQSGSNF0FHV5DP7DM467GHK 2026-03-02T21:02:05.992Z 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)
]]>
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)
]]>
<![CDATA[Delays creating and linking issues from Slack]]> https://linearstatus.com//incidents/01KH1QX4VGG0K72XKM04PVBJ2V 2026-02-09T21:15:27.000Z 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)
]]>
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)
]]>
<![CDATA[Temporary errors creating issues from Slack]]> https://linearstatus.com//incidents/01KG07KH5DGE5Z0FTX0VQZZM77 2026-01-27T14:55:00.000Z Status: Resolved

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.

Affected components
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
]]>
Status: Resolved

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.

Affected components
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
]]>
<![CDATA[Errors creating and updating issues]]> https://linearstatus.com//incidents/01KFASE05HRJWJBCBBVF53X5KJ 2026-01-17T10:00:00.000Z Status: Resolved

On Saturday, we experienced a brief incident where issue creation and issue state changes were unavailable for approximately 1 hour. This was caused by a problem in an internal maintenance process and the impact was limited to some US Hosted Linear workspaces. Additional controls have been put in place to prevent a recurrence and we apologize for the disruption caused.

Affected components
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
]]>
Status: Resolved

On Saturday, we experienced a brief incident where issue creation and issue state changes were unavailable for approximately 1 hour. This was caused by a problem in an internal maintenance process and the impact was limited to some US Hosted Linear workspaces. Additional controls have been put in place to prevent a recurrence and we apologize for the disruption caused.

Affected components
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
]]>
<![CDATA[Issue with outgoing Linear emails]]> https://linearstatus.com//incidents/01KDKG4F4GQWVF5W74XZFS0R02 2025-12-28T21:39:00.000Z Status: Resolved

For a period of 50 minutes, some users did not receive emails from Linear, including login emails. We updated our email service provider. This issue is now resolved.

Affected components
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
]]>
Status: Resolved

For a period of 50 minutes, some users did not receive emails from Linear, including login emails. We updated our email service provider. This issue is now resolved.

Affected components
  • EU Region – Linear application (Operational)
  • EU Region – Integrations (Operational)
  • EU Region – Linear API (Operational)
  • US Region – Linear application (Operational)
  • US Region – Linear API (Operational)
  • US Region – Integrations (Operational)
]]>