LINEAR

⚪ resolved - Linear's issue creation went missing for an hour Saturday thanks to some internal maintenance process that apparently skipped quality control. Turns out even the tool for tracking problems can't track its own problems. At least they added guard rails so this particular comedy show won't get a sequel. (Auto-resolved: no updates in 24h)

⏰ Jan 19, 2026 Fixed (for now) spotted via status_rss

// The official story

Errors creating and updating issues

// Status page says

Status: Resolved On Saturday, we experienced a brief incident where issue creation and issue state changes were unavailable for approximately 1 hour. This was caused by a problem in an internal maintenance process and the impact was limited to some US Hosted Linear workspaces. Additional controls have been put in place to prevent a recurrence and we apologize for the disruption caused. Affected components US Region – Linear a

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

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

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)