Is Linear down?
For agents
proceed
Proceed.
GET upbutler.com/status/linear/status.agent.json
MCP: upstream_status {"service":"linear"}
Issue tracking, its API and webhooks, including agent integrations.
What Linear reports
Operational
Taken as is from Linear's own status page API. Incident titles and component names below are theirs.
Open linearstatus.comUpButler's independent probe
There is no keyless endpoint of Linear that says anything useful, so UpButler does not probe it. To check your own Linear account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Linear components
6 operational
- US Region – Linear applicationOperational
- US Region – Linear APIOperational
- US Region – IntegrationsOperational
- EU Region – Linear applicationOperational
- EU Region – Linear APIOperational
- EU Region – IntegrationsOperational
Linear incidents, last 90 days
1 finished incident seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by Linear.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| EU sync failure | critical | 1 h 6 min |
Tell your outage from Linear's
Declare that your project depends on Linear. When one of your monitors fails while Linear has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- linearcurl -s https://upbutler.com/status/linear/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "linear",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Linear down right now?
- No. As of 2026-10-10 05:07 UTC, Linear is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From Linear's own status page API at https://linearstatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Linear's words.
- How can my agent or app check Linear status?
- Fetch https://upbutler.com/status/linear/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"linear"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Linear's?
- Add "linear" to the dependencies of your UpButler workspace. When one of your monitors fails while Linear has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in code, packages and workflows
UpButler is not affiliated with Linear. Status and incident text belong to Linear and are read from their public status source; the probe result is UpButler's own measurement.