Skip to content

Outage tracker / Linear

Is Linear down?

I'm having a problem

Vendor reports no incidentWhat Linear reports

Linear reports no incident on its status page.

As of the last successful poll, 2026-10-23 23:53 UTC.

Linear's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Awaiting datachecked 3 minutes ago

Our checks of Linear pass from 9 of the 10 regions we check, and have no usable reading from the rest. A missing reading is an absence of data, not an all-clear and not an outage.

As of Oct 23, 2026, 11:58 PM UTC, RealUptime's checks of Linear passed in all 9 regions that returned a reading. RealUptime could not obtain a reading from South America, which is a fact about our own check there and is not evidence about Linear.

Front-door and live API checks

our check readinglive · checked Oct 23, 2026, 11:58 PM UTC
US-East1025 msChecks passing
US-West753 msChecks passing
Europe503 msChecks passing
Asia-Pacific1824 msChecks passing
US-Central290 msChecks passing
Canada241 msChecks passing
UK525 msChecks passing
Southeast Asia755 msChecks passing
Australia460 msChecks passing
South America11687 msAwaiting data
their status pagetheir claim, not our reading

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

from Linear's own status page, checked Oct 23, 2026, 11:41 PM UTC

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
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 597ms2026-10-06 UTC: p95 367ms2026-10-07 UTC: p95 450ms2026-10-08 UTC: p95 368ms2026-10-09 UTC: p95 362ms2026-10-10 UTC: p95 405ms2026-10-11 UTC: p95 423ms2026-10-12 UTC: p95 427ms2026-10-13 UTC: p95 376ms2026-10-14 UTC: p95 352ms2026-10-15 UTC: p95 446ms2026-10-16 UTC: p95 382ms2026-10-17 UTC: p95 774ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 916ms2026-10-21 UTC: p95 956ms2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s
Sep 25Oct 9Oct 24
US-West
1.1sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 1.2s2026-10-06 UTC: p95 580ms2026-10-07 UTC: p95 654ms2026-10-08 UTC: p95 604ms2026-10-09 UTC: p95 488ms2026-10-10 UTC: p95 440ms2026-10-11 UTC: p95 563ms2026-10-12 UTC: p95 546ms2026-10-13 UTC: p95 544ms2026-10-14 UTC: p95 495ms2026-10-15 UTC: p95 604ms2026-10-16 UTC: p95 514ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 962ms2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.1s
Sep 25Oct 9Oct 24
Europe
711msp95 · 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-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 545ms2026-10-06 UTC: p95 571ms2026-10-07 UTC: p95 657ms2026-10-08 UTC: p95 581ms2026-10-09 UTC: p95 552ms2026-10-10 UTC: p95 533ms2026-10-11 UTC: p95 484ms2026-10-12 UTC: p95 481ms2026-10-13 UTC: p95 806ms2026-10-14 UTC: p95 497ms2026-10-15 UTC: p95 648ms2026-10-16 UTC: p95 617ms2026-10-17 UTC: p95 572ms2026-10-18 UTC: p95 781ms2026-10-19 UTC: p95 848ms2026-10-20 UTC: p95 746ms2026-10-21 UTC: p95 776ms2026-10-22 UTC: p95 740ms2026-10-23 UTC: p95 711ms
Sep 25Oct 9Oct 24
Asia-Pacific
1.9sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-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.1s2026-10-06 UTC: p95 1.1s2026-10-07 UTC: p95 941ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 2.2s2026-10-19 UTC: p95 2.4s2026-10-20 UTC: p95 1.9s2026-10-21 UTC: p95 1.9s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.9s
Sep 25Oct 9Oct 24
US-Central
576msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 486ms2026-10-06 UTC: p95 454ms2026-10-07 UTC: p95 413ms2026-10-08 UTC: p95 439ms2026-10-09 UTC: p95 527ms2026-10-10 UTC: p95 537ms2026-10-11 UTC: p95 633ms2026-10-12 UTC: p95 625ms2026-10-13 UTC: p95 438ms2026-10-14 UTC: p95 480ms2026-10-15 UTC: p95 657ms2026-10-16 UTC: p95 705ms2026-10-17 UTC: p95 882ms2026-10-18 UTC: p95 705ms2026-10-19 UTC: p95 704ms2026-10-20 UTC: p95 1.0s2026-10-21 UTC: p95 800ms2026-10-22 UTC: p95 571ms2026-10-23 UTC: p95 576ms
Sep 25Oct 9Oct 24
Canada
575msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 518ms2026-10-06 UTC: p95 770ms2026-10-07 UTC: p95 605ms2026-10-08 UTC: p95 385ms2026-10-09 UTC: p95 500ms2026-10-10 UTC: p95 491ms2026-10-11 UTC: p95 616ms2026-10-12 UTC: p95 555ms2026-10-13 UTC: p95 582ms2026-10-14 UTC: p95 423ms2026-10-15 UTC: p95 435ms2026-10-16 UTC: p95 524ms2026-10-17 UTC: p95 557ms2026-10-18 UTC: p95 535ms2026-10-19 UTC: p95 433ms2026-10-20 UTC: p95 666ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 652ms2026-10-23 UTC: p95 575ms
Sep 25Oct 9Oct 24
UK
775msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-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 684ms2026-10-06 UTC: p95 590ms2026-10-07 UTC: p95 360ms2026-10-08 UTC: p95 593ms2026-10-09 UTC: p95 561ms2026-10-10 UTC: p95 406ms2026-10-11 UTC: p95 582ms2026-10-12 UTC: p95 523ms2026-10-13 UTC: p95 681ms2026-10-14 UTC: p95 485ms2026-10-15 UTC: p95 372ms2026-10-16 UTC: p95 453ms2026-10-17 UTC: p95 487ms2026-10-18 UTC: p95 832ms2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 758ms2026-10-21 UTC: p95 837ms2026-10-22 UTC: p95 712ms2026-10-23 UTC: p95 775ms
Sep 25Oct 9Oct 24
Southeast Asia
1.1sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-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.4s2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.5s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.4s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 2.6s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 1.6s2026-10-23 UTC: p95 1.1s
Sep 25Oct 9Oct 24
Australia
1.2sp95 · 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-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 884ms2026-10-06 UTC: p95 1.3s2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 822ms2026-10-10 UTC: p95 1.2s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.9s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 713ms2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 912ms2026-10-23 UTC: p95 1.2s
Sep 25Oct 9Oct 24
South America
9.7sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-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 563ms2026-10-06 UTC: p95 647ms2026-10-07 UTC: p95 941ms2026-10-08 UTC: p95 863ms2026-10-09 UTC: p95 882ms2026-10-10 UTC: p95 725ms2026-10-11 UTC: p95 905ms2026-10-12 UTC: p95 725ms2026-10-13 UTC: p95 662ms2026-10-14 UTC: p95 742ms2026-10-15 UTC: p95 905ms2026-10-16 UTC: p95 598ms2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 580ms2026-10-19 UTC: p95 582ms2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.4s2026-10-22 UTC: p95 2.9s2026-10-23 UTC: p95 9.7s
Sep 25Oct 9Oct 24
Why some readings show as awaiting data. 2 of 20 readings for Linear came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about Linear's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on Linear

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Awaiting data

Email me when Linear reports an incident on its status page, and again when it reports it resolved.

Get an email when Linear reports an incident

Email me when Linear reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Linear's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 1025msstatus code: 400checked: Oct 23, 2026, 11:53 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
      Checks passinglatency: 753msstatus code: 400checked: Oct 23, 2026, 11:58 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
      Checks passinglatency: 290msstatus code: 400checked: Oct 23, 2026, 11:19 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
      Checks passinglatency: 241msstatus code: 400checked: Oct 23, 2026, 11:21 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
    Awaiting datalatency: 11687msstatus code: nonecheck reading: nonechecked: Oct 23, 2026, 11:01 PM UTC
    0 people in the last 5 minutesNot enough reports to sayLinear refused our South America probe, so we have no reading from there, and a refused probe is not a confirmed outage. We also do not have enough reports from South America to say anything on their own.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 503msstatus code: 400checked: Oct 23, 2026, 11:54 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
      Checks passinglatency: 525msstatus code: 400checked: Oct 23, 2026, 11:21 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1824msstatus code: 400checked: Oct 23, 2026, 11:39 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
      Checks passinglatency: 755msstatus code: 400checked: Oct 23, 2026, 11:21 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
      Checks passinglatency: 460msstatus code: 400checked: Oct 23, 2026, 11:30 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 probe events

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

check 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 check readings and Linear's own claim at the time, side by side.

Full check history for Linear: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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 by RealUptime's checksLive, from this page's own readings.
[![Linear uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

The badge shows the share of our checks that passed over the last 30 days. 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

To cite this page: RealUptime, "Is Linear down?", https://realuptime.io/outages/linear. The readings change with every check, so give the date you read them.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

What we check

primaryfunctional: live API
https://api.linear.app/graphql
secondary
https://linear.app/
secondary
https://linearstatus.com/api/v2/status.json

What our check can and cannot see

A pass means the service's servers answered our request with the error they give a request that carries no account or valid input. It does not show that sign-in works or that any real request succeeds.

Host checked: api.linear.app

RealUptime is not affiliated with Linear; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.