Delayed actions for Linear agent and loops automations
Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.
The latest update from Linear.
State
Resolved
Started
74 d ago
2026-08-19 15:26 UTC
Lasted
16 min
until 2026-08-19 15:42 UTC
Worst impact
Degraded
Timeline
2 updatesInvestigating
16 min 100%
Updates
Times in UTCAs posted by Linear
Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.
Some customers may experience delayed responses from Linear agent and delayed runs for automated actions through Loops. We're investigating this issue now and will share an update as soon as possible.
Linear in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
12
Median duration
56 min
This incident
71% shorter than the median
Other Linear incidents
All incidentsLinear·Project pages failing to load
Normal functionality has resumed, you may need to refresh Linear (Mac: ⌘+R / Windows: CTRL+R)
Linear·Some Slack integrations have been unexpectedly archived
> We’ve deployed a fix for the issue that unexpectedly disconnected Slack integrations in some workspaces. > > If your integration remains disconnected, reconnect it in Linear under **Settings → Integrations → Slack**, then add Linear back to affected channels using `/invite @Linear`. Your notification settings and project channel links will return automatically. > > We’re sorry for the disruption and the extra steps needed to restore your integration.
Linear·Problems loading application
Normal functionality has resumed.
Linear·EU sync failure
We've published a post mortem with details on this incident including a timeline of events and prevention steps for the future:
Linear·Degraded performance in US region workspaces
Normal levels of operation has been fully restored. Incident is now resolved and closed.
Follow Linear
Your coding agent knows when Linear is down, and tells you when a failure is theirs, not yours. You can also get Linear incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "linear" and tell me if Linear has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=linear/feed subscribe https://outages.cc/feed.xml?providers=linearFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane