- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 27of 100
What to do
Check whether your product depends on Linear. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 25m it lasted.
Anything that failed between 2026-06-17 22:52 UTC and 2026-06-17 23:17 UTC may need a replay.Subscribe to Linear's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=linear works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Linear 3
- investigating
We're investigating reports of general latency when taking actions in Linear — we're working to confirm the suspected root cause and remediate the degradation. We'll provide updates as we have them.
provider
- monitoring
We’ve rolled back a recent change that may have contributed to the slowdown and performance is improving. We’re keeping a close eye on continued recovery.
provider
- resolved
The increased latency has been resolved, and Linear should be operating normally again. We rolled back the query change that caused the slowdown and have confirmed performance has recovered.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-09094c0180
Is Linear still down?
No, this incident was resolved 2026-06-17 23:17 UTC. For Linear's live state, see https://down.guide/linear.
How long did it last?
25m, from 2026-06-17 22:52 UTC to 2026-06-17 23:17 UTC, by the times Linear posted.
What caused it?
Linear hasn't published a root cause. If it does, it shows here.
Where does this come from?
Linear's official status page, https://linearstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.