Degraded performance in US region workspaces
Normal levels of operation has been fully restored. Incident is now resolved and closed.
The latest update from Linear.
State
Resolved
Started
57 d ago
2026-09-05 15:17 UTC
Lasted
56 min
until 2026-09-05 16:13 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
16 min 29%
Monitoring
39 min 71%
Updates
Times in UTCAs posted by Linear
Normal levels of operation has been fully restored. Incident is now resolved and closed.
Normal levels of operation have resumed, we'll continue to monitor the situation before marking fully resolved.
Linear's services(in particular the API and MCP server) are currently impacted for some users hosted in the US region. Our team is investigating and will provide an update shortly.
Linear in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
12
Median duration
56 min
This incident
About 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·Increased failures and latency for Android push notifications
Normal functionality has resumed.
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