Degraded performance with the MCP connector
The Linear MCP connector has degraded performance and returns connection errors. Linear reports that the problem comes from a downstream provider. Linear is monitoring the provider status.
State
Monitoring
Started
Ongoing for
36 min
Worst impact
Degraded
Timeline
1 updateMonitoring
36 min 100%
Updates
Times in UTCAs posted by Linear
We're monitoring an downstream provider issue that's causing errors connecting to the Linear MCP. We will monitor the providers status and update ours accordingly.
Linear in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
9
Median duration
56 min
This incident
35% shorter than the median
Other Linear incidents
All incidentsLinear·Issues authorising new integration connections
Linear had issues authorising new integration connections. Linear reports that the issue is resolved. The outage lasted 24 minutes.
Linear·Slack integration degraded due to Slack outage
Linear's Slack integration had degraded performance, including failures and delays when users created linked Slack channels. Linear reports that the incident is resolved. It lasted 3 hours and 10 minutes.
Linear·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.
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