https://linearstatus.com/Linear status2026-03-16T23:52:02.946Zincident.ioLinear status page updateshttps://storage.googleapis.com/incident-io-status-page-logos/01F3XM6VBTA29DFRAPT6VQZZ6K/linear/vvd2ez05.pnghttps://linearstatus.com//incidents/01KKE983BSMR04B1F4EK2RSAFK2026-03-12T13:22:57.096ZStatus: 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.
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.
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].
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.
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.
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.
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.