← Back to the carnage
LINEAR

⚪ Linear's background jobs in EU took an unplanned nap from 12:45-13:05 UTC after the autoscaler decided less capacity = more vibes. Apparently nobody told the infrastructure that 'downsizing' doesn't work the same way in tech as it does in HR. All fixed now, assuming it doesn't get ideas again. (Auto-resolved: no updates in 24h)

⏰ May 25, 2026 Fixed (for now) spotted via status_rss

// The official story

Resolved - Delayed background processing for some users in EU region

// Status page says

Status: Resolved Task processing in our EU region was briefly delayed from 12:45 to 13:05 UTC after capacity scaled down too far, which slowed some background actions from completing normally. We scaled capacity back up and processing has recovered. Service should now be operating normally. Affected components US Region – Linear API (Operational) US Region – Integrations (Operational) EU Region – Linear applicatio

🔗 Official status page (for the PR-approved version)

https://linearstatus.com//incidents/01KSFN3TVDAWZVGN319RED8DE5

Linear's Greatest Hits

🟢 LINEAR Sep 27, 2026
🟡 Linear's European infrastructure decided to ghost its entire region. The app is fully down while engineers perform archaeological digs through the logs. Thoughts and prayers to anyone's sprint planning today. (Auto-resolved: no updates in 24h)
🟢 LINEAR Aug 13, 2026
🟡 Linear's Codex stopped accepting new sessions because OpenAI's infrastructure decided to take an unscheduled sabbatical. Apparently 'investigating' is tech-speak for 'we're reading the error logs for the first time.'. (Auto-resolved: no updates in 24h)
🟢 LINEAR Jul 16, 2026
🟡 Linear decided to explore the concept of 'eventual consistency' by making some US customers wait indefinitely. The app's now in that special state between 'working' and 'performance art installation.'. (Auto-resolved: no updates in 24h)
🟢 LINEAR Jun 30, 2026
🟡 Linear's having an existential crisis about regional routing—some India users can't load the app while EU infrastructure takes a nap. Integrations and API equally uncooperative. Engineering team is investigating what appears to be a coordinated refusal to work. (Auto-resolved: no updates in 24h)