Slack integration degraded due to Slack outage
Slack-related functions in Linear do not work or are slow. This includes the creation of linked Slack channels. Linear reports that the functions are in recovery and Linear monitors the situation. The incident started 98 minutes ago.
State
Monitoring
Started
Ongoing for
2 h 14 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
10 min 8%
Monitoring
2 h 4 min 92%
Updates
Times in UTCAs posted by Linear
Slack-related functionality in Linear continues to show normal activity. Slack reports improved service and is continuing recovery work. We’re monitoring the situation while Slack completes its recovery.
Slack-related functionality in Linear is recovering following the Slack outage. Creating linked Slack channels is working again, though some users may still experience intermittent issues. We’re continuing to monitor recovery and will share updates here as they become available.
An ongoing Slack outage is causing failures or delays in Slack-related functionality in Linear, including creating linked Slack channels. We’re seeing signs of recovery and are monitoring the situation.
Linear in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
9
Median duration
56 min
This incident
2.4× 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.live/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.live/feed.xml?providers=linear/feed subscribe https://outages.live/feed.xml?providers=linearFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane