Skip to content

Outage tracker / Linear

Is Linear down?

I'm having a problem

Operationalchecked 3 minutes ago

We reached Linear from all 10 regions we check.

As of Oct 5, 2026, 8:12 PM UTC, Linear answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 44 days we have measured Linear (since Aug 22, 2026).

our independent probeslive · checked Oct 5, 2026, 8:12 PM UTC
US-East289 msOperational
US-West498 msOperational
Europe306 msOperational
Asia-Pacific483 msOperational
US-Central305 msOperational
Canada254 msOperational
UK284 msOperational
Southeast Asia1173 msOperational
Australia1355 msOperational
South America407 msOperational
their status pagetheir claim, not our reading

Linear reports: All systems operational (“All Systems Operational”)

from Linear's own status page, checked Oct 5, 2026, 7:58 PM UTC
Our probes and Linear's own status page agree: both show Linear as reachable right now.

Linear's own component breakdown, as they publish it

  • US Region – Linear applicationOperational
  • US Region – Linear APIOperational
  • US Region – IntegrationsOperational
  • EU Region – Linear applicationOperational
  • EU Region – Linear APIOperational
  • EU Region – IntegrationsOperational

These are Linear's components, named and scored by Linear. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Linear's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Linear response time, by region

US-East
695msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 355ms2026-09-07 UTC: p95 494ms2026-09-08 UTC: p95 422ms2026-09-09 UTC: p95 462ms2026-09-10 UTC: p95 308ms2026-09-11 UTC: p95 872ms2026-09-12 UTC: p95 220ms2026-09-13 UTC: p95 198ms2026-09-14 UTC: p95 251ms2026-09-15 UTC: p95 310ms2026-09-16 UTC: p95 363ms2026-09-17 UTC: p95 387ms2026-09-18 UTC: p95 334ms2026-09-19 UTC: p95 251ms2026-09-20 UTC: p95 297ms2026-09-21 UTC: p95 283ms2026-09-22 UTC: p95 294ms2026-09-23 UTC: p95 302ms2026-09-24 UTC: p95 631ms2026-09-25 UTC: p95 335ms2026-09-26 UTC: p95 398ms2026-09-27 UTC: p95 416ms2026-09-28 UTC: p95 500ms2026-09-29 UTC: p95 480ms2026-09-30 UTC: p95 418ms2026-10-01 UTC: p95 380ms2026-10-02 UTC: p95 419ms2026-10-03 UTC: p95 347ms2026-10-04 UTC: p95 366ms2026-10-05 UTC: p95 695ms
Sep 6Sep 20Oct 5
US-West
735msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 369ms2026-09-07 UTC: p95 484ms2026-09-08 UTC: p95 410ms2026-09-09 UTC: p95 349ms2026-09-10 UTC: p95 407ms2026-09-11 UTC: p95 511ms2026-09-12 UTC: p95 320ms2026-09-13 UTC: p95 397ms2026-09-14 UTC: p95 412ms2026-09-15 UTC: p95 589ms2026-09-16 UTC: p95 490ms2026-09-17 UTC: p95 615ms2026-09-18 UTC: p95 793ms2026-09-19 UTC: p95 347ms2026-09-20 UTC: p95 456ms2026-09-21 UTC: p95 657ms2026-09-22 UTC: p95 698ms2026-09-23 UTC: p95 597ms2026-09-24 UTC: p95 546ms2026-09-25 UTC: p95 653ms2026-09-26 UTC: p95 607ms2026-09-27 UTC: p95 400ms2026-09-28 UTC: p95 467ms2026-09-29 UTC: p95 483ms2026-09-30 UTC: p95 679ms2026-10-01 UTC: p95 562ms2026-10-02 UTC: p95 452ms2026-10-03 UTC: p95 515ms2026-10-04 UTC: p95 554ms2026-10-05 UTC: p95 735ms
Sep 6Sep 20Oct 5
Europe
568msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 562ms2026-09-07 UTC: p95 516ms2026-09-08 UTC: p95 454ms2026-09-09 UTC: p95 427ms2026-09-10 UTC: p95 756ms2026-09-11 UTC: p95 535ms2026-09-12 UTC: p95 600ms2026-09-13 UTC: p95 794ms2026-09-14 UTC: p95 606ms2026-09-15 UTC: p95 527ms2026-09-16 UTC: p95 624ms2026-09-17 UTC: p95 467ms2026-09-18 UTC: p95 531ms2026-09-19 UTC: p95 475ms2026-09-20 UTC: p95 576ms2026-09-21 UTC: p95 446ms2026-09-22 UTC: p95 604ms2026-09-23 UTC: p95 603ms2026-09-24 UTC: p95 628ms2026-09-25 UTC: p95 557ms2026-09-26 UTC: p95 643ms2026-09-27 UTC: p95 520ms2026-09-28 UTC: p95 618ms2026-09-29 UTC: p95 509ms2026-09-30 UTC: p95 690ms2026-10-01 UTC: p95 608ms2026-10-02 UTC: p95 581ms2026-10-03 UTC: p95 452ms2026-10-04 UTC: p95 737ms2026-10-05 UTC: p95 568ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 946ms2026-09-07 UTC: p95 875ms2026-09-08 UTC: p95 955ms2026-09-09 UTC: p95 970ms2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 862ms2026-09-12 UTC: p95 976ms2026-09-13 UTC: p95 822ms2026-09-14 UTC: p95 575ms2026-09-15 UTC: p95 857ms2026-09-16 UTC: p95 714ms2026-09-17 UTC: p95 878ms2026-09-18 UTC: p95 910ms2026-09-19 UTC: p95 815ms2026-09-20 UTC: p95 872ms2026-09-21 UTC: p95 929ms2026-09-22 UTC: p95 911ms2026-09-23 UTC: p95 870ms2026-09-24 UTC: p95 887ms2026-09-25 UTC: p95 910ms2026-09-26 UTC: p95 959ms2026-09-27 UTC: p95 930ms2026-09-28 UTC: p95 869ms2026-09-29 UTC: p95 1.0s2026-09-30 UTC: p95 939ms2026-10-01 UTC: p95 887ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 919ms2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
513msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 416ms2026-09-07 UTC: p95 371ms2026-09-08 UTC: p95 506ms2026-09-09 UTC: p95 533ms2026-09-10 UTC: p95 448ms2026-09-11 UTC: p95 566ms2026-09-12 UTC: p95 517ms2026-09-13 UTC: p95 649ms2026-09-14 UTC: p95 441ms2026-09-15 UTC: p95 350ms2026-09-16 UTC: p95 508ms2026-09-17 UTC: p95 353ms2026-09-18 UTC: p95 380ms2026-09-19 UTC: p95 558ms2026-09-20 UTC: p95 370ms2026-09-21 UTC: p95 370ms2026-09-22 UTC: p95 523ms2026-09-23 UTC: p95 602ms2026-09-24 UTC: p95 535ms2026-09-25 UTC: p95 424ms2026-09-26 UTC: p95 592ms2026-09-27 UTC: p95 512ms2026-09-28 UTC: p95 644ms2026-09-29 UTC: p95 734ms2026-09-30 UTC: p95 618ms2026-10-01 UTC: p95 527ms2026-10-02 UTC: p95 376ms2026-10-03 UTC: p95 269ms2026-10-04 UTC: p95 484ms2026-10-05 UTC: p95 513ms
Sep 6Sep 20Oct 5
Canada
542msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 337ms2026-09-07 UTC: p95 393ms2026-09-08 UTC: p95 498ms2026-09-09 UTC: p95 275ms2026-09-10 UTC: p95 424ms2026-09-11 UTC: p95 623ms2026-09-12 UTC: p95 539ms2026-09-13 UTC: p95 608ms2026-09-14 UTC: p95 613ms2026-09-15 UTC: p95 674ms2026-09-16 UTC: p95 606ms2026-09-17 UTC: p95 467ms2026-09-18 UTC: p95 398ms2026-09-19 UTC: p95 517ms2026-09-20 UTC: p95 519ms2026-09-21 UTC: p95 859ms2026-09-22 UTC: p95 712ms2026-09-23 UTC: p95 688ms2026-09-24 UTC: p95 820ms2026-09-25 UTC: p95 905ms2026-09-26 UTC: p95 312ms2026-09-27 UTC: p95 417ms2026-09-28 UTC: p95 536ms2026-09-29 UTC: p95 447ms2026-09-30 UTC: p95 565ms2026-10-01 UTC: p95 472ms2026-10-02 UTC: p95 387ms2026-10-03 UTC: p95 454ms2026-10-04 UTC: p95 494ms2026-10-05 UTC: p95 542ms
Sep 6Sep 20Oct 5
UK
706msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 732ms2026-09-07 UTC: p95 338ms2026-09-08 UTC: p95 408ms2026-09-09 UTC: p95 434ms2026-09-10 UTC: p95 631ms2026-09-11 UTC: p95 772ms2026-09-12 UTC: p95 434ms2026-09-13 UTC: p95 474ms2026-09-14 UTC: p95 391ms2026-09-15 UTC: p95 437ms2026-09-16 UTC: p95 699ms2026-09-17 UTC: p95 370ms2026-09-18 UTC: p95 375ms2026-09-19 UTC: p95 571ms2026-09-20 UTC: p95 587ms2026-09-21 UTC: p95 444ms2026-09-22 UTC: p95 510ms2026-09-23 UTC: p95 648ms2026-09-24 UTC: p95 448ms2026-09-25 UTC: p95 709ms2026-09-26 UTC: p95 628ms2026-09-27 UTC: p95 391ms2026-09-28 UTC: p95 654ms2026-09-29 UTC: p95 751ms2026-09-30 UTC: p95 819ms2026-10-01 UTC: p95 464ms2026-10-02 UTC: p95 493ms2026-10-03 UTC: p95 479ms2026-10-04 UTC: p95 669ms2026-10-05 UTC: p95 706ms
Sep 6Sep 20Oct 5
Southeast Asia
1.3sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 978ms2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.9s2026-09-13 UTC: p95 1.9s2026-09-14 UTC: p95 1.7s2026-09-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.4s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.5s2026-09-21 UTC: p95 1.3s2026-09-22 UTC: p95 1.9s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.4s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.7s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.6s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
Australia
909msp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.4s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 736ms2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.5s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.7s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.0s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 924ms2026-09-26 UTC: p95 1.4s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.6s2026-09-29 UTC: p95 955ms2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 913ms2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 974ms2026-10-05 UTC: p95 909ms
Sep 6Sep 20Oct 5
South America
560msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 575ms2026-09-07 UTC: p95 586ms2026-09-08 UTC: p95 787ms2026-09-09 UTC: p95 774ms2026-09-10 UTC: p95 620ms2026-09-11 UTC: p95 942ms2026-09-12 UTC: p95 734ms2026-09-13 UTC: p95 705ms2026-09-14 UTC: p95 830ms2026-09-15 UTC: p95 1.0s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 838ms2026-09-19 UTC: p95 562ms2026-09-20 UTC: p95 551ms2026-09-21 UTC: p95 542ms2026-09-22 UTC: p95 807ms2026-09-23 UTC: p95 859ms2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.1s2026-09-26 UTC: p95 863ms2026-09-27 UTC: p95 1.1s2026-09-28 UTC: p95 875ms2026-09-29 UTC: p95 990ms2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 981ms2026-10-02 UTC: p95 1.3s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 560ms
Sep 6Sep 20Oct 5

Is it Linear, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Linear -- it cannot diagnose Linear's own systems.

What we measured, function by function

Linear answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational

Get an email when we see Linear go down, and when it is back

Get told when we measure this

We will tell you when our probes stop reaching Linear, and again when they can reach it again. That is our own measurement from ten regions, not Linear's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 289msstatus code: 400checked: Oct 5, 2026, 7:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Linear normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 498msstatus code: 400checked: Oct 5, 2026, 7:47 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Linear normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 305msstatus code: 400checked: Oct 5, 2026, 8:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Linear normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 254msstatus code: 400checked: Oct 5, 2026, 8:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Linear normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 407msstatus code: 400checked: Oct 5, 2026, 7:17 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Linear normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 306msstatus code: 400checked: Oct 5, 2026, 7:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Linear normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 284msstatus code: 400checked: Oct 5, 2026, 8:07 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Linear normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 483msstatus code: 400checked: Oct 5, 2026, 7:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Linear normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1173msstatus code: 400checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Linear normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1355msstatus code: 400checked: Oct 5, 2026, 7:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Linear normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Linear, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Linear yet, which is not evidence that nothing is wrong.

Recent outages

EU sync failure, 1h 6mdeclared on their status page2026-09-27
Degraded performance in US region workspaces, 56mdeclared on their status page2026-09-05
Increased failures and latency for Android push notifications, 1h 56mdeclared on their status page2026-09-01
Delayed actions for Linear agent and loops automations, 16mdeclared on their status page2026-08-19
Documentation site failing to load, 2mdeclared on their status page2026-08-12
Codex integration sessions failing to start, 110h 27mdeclared on their status page2026-08-10
Some customers are seeing issues with Linear loading, 1h 33mdeclared on their status page2026-07-16
App not loading for some users in India, 1h 32mdeclared on their status page2026-06-30

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Linear since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Linear covering any window you pick, with our measurements and Linear's own claim at the time, side by side.

Full availability history for Linear: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Put this badge in your README

Linear uptime measured by RealUptimeLive, from this page's own readings.
[![Linear uptime measured by RealUptime](https://realuptime.io/outages/linear/badge.svg?days=30)](https://realuptime.io/outages/linear)
<a href="https://realuptime.io/outages/linear"><img src="https://realuptime.io/outages/linear/badge.svg?days=30" alt="Linear uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Linear's SLA implies, from our measurement

At or above your target

We measured none of downtime for Linear over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Linear's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.linear.app/graphql
secondary
https://linear.app/
secondary
https://linearstatus.com/api/v2/status.json
RealUptime is not affiliated with Linear; the name identifies what we measured, and nothing here speaks for Linear's own team. We send a single web request to Linear from 10 regions on our own schedule and time the response. We do not see inside Linear's systems, do not use an account or real transaction, and are not the same signal Linear's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Linear is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.