← Back to Linear's check readings
We started checking Linear on August 22, 2026, which is 51 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Linear reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Linear's own status page declared. Below it, any public chatter we saw about Linear and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Linear's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Linear in the last 24 hours, which is not evidence that nothing is wrong.
Linear's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Linear's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Linear next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Linear's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
EU sync failureMajor outage
Sep 27, 2026, 10:56 AM UTC to Sep 27, 2026, 12:02 PM UTC (1h 6m)resolved
their latest update (Oct 1, 2026, 5:50 PM UTC): We've published a post mortem with details on this incident including a timeline of events and prevention steps for the future: <https://linear.app/docs/eu-sync-outage>
Degraded performance in US region workspacesMinor incident
Sep 5, 2026, 3:17 PM UTC to Sep 5, 2026, 4:13 PM UTC (56 min)resolved
their latest update (Sep 5, 2026, 4:13 PM UTC): Normal levels of operation has been fully restored. Incident is now resolved and closed.
Increased failures and latency for Android push notificationsMinor incident
Sep 1, 2026, 10:27 AM UTC to Sep 1, 2026, 12:23 PM UTC (1h 56m)resolved
their latest update (Sep 1, 2026, 12:23 PM UTC): Normal functionality has resumed.
Delayed actions for Linear agent and loops automationsMinor incident
Aug 19, 2026, 3:26 PM UTC to Aug 19, 2026, 3:42 PM UTC (16 min)resolved
their latest update (Aug 19, 2026, 3:42 PM UTC): Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.
Documentation site failing to loadAll systems operational
Aug 12, 2026, 4:01 PM UTC to Aug 12, 2026, 4:03 PM UTC (2 min)resolved
their latest update (Aug 12, 2026, 4:03 PM UTC): Documentation site now loads after refreshing.
Codex integration sessions failing to startAll systems operational
Aug 10, 2026, 3:54 AM UTC to Aug 14, 2026, 6:21 PM UTC (4d 14h)resolved
their latest update (Aug 14, 2026, 6:21 PM UTC): The connection between Linear and OpenAI was failing and has now been rectified.
Some customers are seeing issues with Linear loadingPartial outage
Jul 16, 2026, 4:47 PM UTC to Jul 16, 2026, 6:20 PM UTC (1h 33m)resolved
their latest update (Jul 16, 2026, 6:20 PM UTC): Recent feature roll-outs added extra load to our databases, and a fix has been implemented. Thank you for your patience while we worked to resolve this.
App not loading for some users in IndiaPartial outage
Jun 30, 2026, 8:12 PM UTC to Jun 30, 2026, 9:44 PM UTC (1h 32m)resolved
their latest update (Jun 30, 2026, 9:44 PM UTC): An upstream regional networking issue impacted access for some Linear users in India.
The issue has now been resolved, and our service is operating normally for all regions.
Some customers experiencing issues with Linear loading and syncingPartial outage
Jun 22, 2026, 3:27 PM UTC to Jun 22, 2026, 6:15 PM UTC (2h 48m)resolved
their latest update (Jun 22, 2026, 6:15 PM UTC): Some customers were experiencing issues with Linear loading and syncing. Performance has returned to normal, and the issue is resolved. We appreciate your patience while we worked on this.
EU sync delays for some workspacesMinor incident
Jun 22, 2026, 10:27 AM UTC to Jun 22, 2026, 11:00 AM UTC (33 min)resolved
their latest update (Jun 22, 2026, 11:00 AM UTC): Some users with EU-hosted workspaces experienced delays syncing changes for a short period of time this morning. Sync performance has returned to normal, and the issue is resolved. Thank you for your patience while we worked on this.
Showing the 10 most recent of 28 incidents Linear has declared in the history we hold.
These entries are Linear's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Linear's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.