Loading status…
Loading status…
Linear status · Collaboration · checked (46s ago)
No — Linear is not down. All Linear systems are reported operational.
According to Linear's official status page, Linear was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Linear's feed reported no outage in 100.00% of our checks.
Everything above is read from Linear's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Linear in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Linear is an issue tracker and project planning tool built for software teams, known for a fast client that syncs in the background. Issues, cycles and projects live in Linear's service, with a GraphQL API that teams wire into their deploy and support tooling.
Linear's status page separates the API and sync layer from integrations with GitHub, Slack and the rest. The sync layer is the interesting one: Linear's client keeps a local cache and works optimistically, so a sync outage looks like changes not appearing for teammates rather than the app failing outright.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Linear's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Linear was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 46s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Linear's status endpoint.
Linear has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Linear posted itself — not every problem users hit.
resolved · Sep 5, 03:17 PM (14d ago)
resolved · Sep 1, 10:27 AM (18d ago)
resolved · Aug 19, 03:26 PM (31d ago)
resolved · Aug 12, 04:01 PM (38d ago)
resolved · Aug 10, 03:54 AM (41d ago)
resolved · Jul 16, 04:47 PM (65d ago)
resolved · Jun 30, 08:12 PM (81d ago)
resolved · Jun 22, 03:27 PM (89d ago)
resolved · Jun 22, 10:27 AM (89d ago)
resolved · Jun 17, 10:52 PM (94d ago)
resolved · Jun 17, 05:05 PM (94d ago)
resolved · Jun 16, 03:05 PM (95d ago)
resolved · Jun 15, 10:58 AM (96d ago)
resolved · Jun 9, 05:08 PM (102d ago)
resolved · Jun 4, 12:49 PM (107d ago)
resolved · Jun 3, 02:07 PM (108d ago)
resolved · May 31, 06:49 PM (111d ago)
resolved · May 28, 02:25 PM (114d ago)
resolved · May 28, 01:45 PM (114d ago)
resolved · May 25, 01:27 PM (117d ago)
If your own changes appear but nobody else's do, that is the sync layer, and reloading will not fix it. Integration failures — an issue not closing from a commit message, a Slack notification not arriving — are usually the other service or a revoked token. API rate limits apply per workspace and are easy to exceed from an automation running in a loop.
Linear is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.