Skip to main content

Is Linear Down?

No — Linear is up

Reachable from all 8 checked regions

Average response time: 286ms

Last checked · checks run every 6 hours

Official status page: https://linearstatus.com

Linear uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
354ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 31 checks
Aug 4: 100.00% uptime, 31 checks
Aug 5: 100.00% uptime, 45 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 30 checks
Aug 9: 100.00% uptime, 31 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 30 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 32 checks
Aug 18: 100.00% uptime, 40 checks
Jul 20 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
455ms
DNS 0ms TCP 2ms TLS 17ms TTFB 425ms
bom
465ms
DNS 1ms TCP 3ms TLS 16ms TTFB 431ms
cdg
317ms
DNS 0ms TCP 1ms TLS 11ms TTFB 299ms
dfw
122ms
DNS 0ms TCP 1ms TLS 11ms TTFB 104ms
ewr
119ms
DNS 0ms TCP 2ms TLS 14ms TTFB 99ms
fra
248ms
DNS 0ms TCP 1ms TLS 11ms TTFB 228ms
gru
213ms
DNS 0ms TCP 2ms TLS 13ms TTFB 185ms
iad
91ms
DNS 0ms TCP 1ms TLS 11ms TTFB 72ms
jnb
716ms
DNS 0ms TCP 0ms TLS 9ms TTFB 696ms

What Linear does

Linear is an issue tracker and planning tool used mainly by software teams, covering issues, cycles, projects and roadmaps. Engineering teams run day-to-day triage in it and wire it into GitHub, Slack and deployment tooling, so an outage interrupts planning and coordination rather than taking down anything a customer touches.

What an outage looks like

Linear reports its application and its API separately for each region, so the web and desktop clients can fail while API integrations keep working, or the reverse. Changes may stop syncing between teammates before anything shows an obvious error. Integrations that write into Linear, such as Slack and GitHub automations, stop moving issues along while the API component is affected.

What to do about it

Check linearstatus.com, which is where status.linear.app points. It reports the Linear application and the Linear API separately by region, with uptime percentages across a rolling three-month window rather than a single pill. Independent monitors sometimes disagree with it, so if the page reads healthy during an obvious failure, make sure you are reading the line for your own region.

Is it down for everyone, or just you?

If this page says Linear is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Linear outage FAQ

Is Linear down for my region or everywhere?
Linear reports by region, so read the line that matches yours. Its status page lists the application and the API separately for each region with individual uptime percentages, which means a US incident does not imply a problem elsewhere. Teams spread across regions can genuinely see different behaviour during the same incident.
Do Slack and GitHub integrations break when Linear is down?
They stop updating issues whenever the API component is affected, even if the app itself loads fine. Linear tracks the application and the API on separate lines, and integrations talk to the API rather than the client. If pull requests are no longer moving issues along but the app opens normally, read the API line instead.
Why do outage trackers disagree with Linear's own status page?
Independent monitors measure continuously from outside, while a vendor status page changes when a person or an automation declares an incident. Short or partial problems often reach the former first and sometimes never reach the latter at all. Disagreement between the two is ordinary rather than evidence that either one is broken.
How much history does Linear's status page keep?
A rolling window of roughly three months, labelled with the month range, giving an uptime percentage per component rather than only a current state. That is enough to see whether a particular component has been repeatedly troublesome, though not enough to compare one quarter against another.

How we measure this

  • We request Linear's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Linear publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Linear goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required