Vendor Status Watch

← all vendors

Linear status history

Current state: operational — “All Systems Operational” per https://linearstatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
9incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:
Get Linear alerts in your Slack — free templateRSS for Linear

How long do Linear incidents last?

54 minmedian incident duration24 measured
3.0 h90th percentile1 in 10 ran longer
78 minmedian, major/critical only6 incidents

From 24 incidents with a vendor-posted start and resolve time. Longest on record: Codex integration sessions failing to start — 4.6 days (2026-08-10 03:54 UTC). Excluded, never estimated: 2 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (26)

StartedIncidentStatusImpactDuration
2026-09-05 15:17 UTCDegraded performance in US region workspacesresolvedminor55 min
2026-09-01 10:27 UTCIncreased failures and latency for Android push notificationsresolvedminor1 h 56 min
2026-08-19 15:26 UTCDelayed actions for Linear agent and loops automationsresolvedminor15 min
2026-08-12 16:01 UTCDocumentation site failing to loadresolvednone1 min
2026-08-10 03:54 UTCCodex integration sessions failing to startresolvednone4 d 14 h
2026-07-16 16:47 UTCSome customers are seeing issues with Linear loadingresolvedmajor1 h 32 min
2026-06-30 20:12 UTCApp not loading for some users in Indiaresolvedmajor1 h 31 min
2026-06-22 15:27 UTCSome customers experiencing issues with Linear loading and syncingresolvedmajor2 h 48 min
2026-06-22 10:27 UTCEU sync delays for some workspacesresolvedminor33 min
2026-06-17 22:52 UTCIncreased latency while using Linearresolvedminor24 min
2026-06-17 17:05 UTCSome users may experience errors loading code diffsresolvedminor2 h 58 min
2026-06-16 15:05 UTCSome customers seeing delays resolvedminor6 h 49 min
2026-06-15 10:58 UTCProblems with right-clicking or opening context menus on issuesresolvedminor5 min
2026-06-09 17:08 UTCPartial Linear outageresolvedminor40 min
2026-06-04 12:49 UTCIn-App Contact Form experiencing issuesresolvedminor2 h 20 min
2026-06-03 14:07 UTCLinear Agent code intelligence tools failing to runresolvedminor11 min
2026-05-31 18:49 UTCDelays affecting event processing in our US regionresolvednone1 h 14 min
2026-05-28 14:25 UTCLinear not loading for some usersresolvedcritical56 min
2026-05-28 13:45 UTCAsks Email Intake failingresolvedcritical31 min
2026-05-25 13:27 UTCResolved - Delayed background processing for some users in EU regionresolvednone—
2026-05-22 08:34 UTCResolved: Degraded search quality for some US workspacesresolvednone—
2026-05-19 04:02 UTCInvestigating delays in background processingresolvedminor54 min
2026-05-18 21:43 UTCErrors affecting workspaces using cyclesresolvedminor14 min
2026-05-14 14:51 UTCDegraded Slack integration performanceresolvedmajor1 h 06 min
2026-05-12 15:23 UTCElevated latency affecting updates in Linearresolvedminor30 min
2026-04-22 13:13 UTCLinear agent intermittently unresponsive in Slackresolvedminor13 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Linear with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "linear"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}