On this page
Is Linear Down? How to Tell and What to Do
Linear is the issue tracker for engineering teams that move fast — sprints, cycles, triage queues, and roadmaps all live there. When Linear degrades, your team's coordination breaks silently: tickets stop loading, syncs hang, webhooks miss.
Statusfield brings reported Linear incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Linear incidents with your team
Statusfield brings reported status for Linear together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of a Linear Outage
| Symptom | What's likely happening |
|---|---|
| Issues and cycles not loading | App server or database layer is degraded |
| Comments or updates not saving | Write API is failing |
| Slack or GitHub sync not triggering | Webhook or integration pipeline is down |
| Search returning stale or empty results | Search indexing is lagging |
| Cycle progress not updating | Background job processing is degraded |
| CLI or API returning 502 / 503 | Backend infrastructure is overloaded |
| Notifications not arriving | Email or push notification delivery is failing |
How to Confirm It's Linear, Not You
Before blaming the network or your browser:
1. Check Linear's API directly
curl -I https://api.linear.app/graphqlA 200 or 405 response means the API endpoint is reachable. A 502, 503, or connection timeout indicates a platform issue.
2. Test in an incognito window
Browser extensions or cached sessions can cause issues that look like outages. Open Linear in an incognito/private window to eliminate local state.
3. Verify which feature is affected
Linear has distinct systems for issue viewing, comments, search, and integrations. A degraded search index doesn't mean the write API is broken. Isolate which action is failing before escalating.
4. Check Linear's GitHub integration separately
Linear ↔ GitHub syncs run through a separate integration pipeline. If GitHub PR links aren't updating but Linear itself loads fine, the issue is the integration layer, not Linear's core.
Use vendor reports as investigation context
Statusfield brings reported Linear incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.
What to Do During a Linear Outage
Immediate (first 5 minutes)
- Identify the affected surface — is it reading (issues won't load), writing (saves fail), or integrations (GitHub/Slack sync broken)? Each has a different workaround.
- Establish a temporary coordination channel — if Linear is fully down, designate a Slack channel or shared doc as the incident coordination point so work isn't blocked.
- Note the exact start time — critical for reconciling any tickets or updates that need to be re-entered after recovery.
- Check if API access still works — Linear's API sometimes stays partially functional when the web app is degraded; CLI tools or integrations may still operate.
Communication (first 15 minutes)
- Alert your engineering team that Linear is degraded so they stop retrying and wasting time.
- If a sprint cycle is closing or planning is in progress, defer the ceremony until Linear recovers — partial data is worse than no data.
- Capture any critical decisions being made verbally so they can be entered into Linear once it recovers.
Recovery
- After Linear recovers, verify that any comments or updates submitted during the degradation were actually saved — some may have silently failed.
- Check GitHub ↔ Linear sync to confirm no PR → issue links were dropped during the outage window.
- Review webhook logs if your team uses Linear webhooks to trigger automation.
Linear Components and What Each Outage Looks Like
| Component | Impact when degraded |
|---|---|
| App server | Issues, projects, and cycles won't load |
| Write API | Comments, status changes, and new issues fail to save |
| Search index | Search returns stale results or times out |
| GitHub integration | PR → issue links stop updating; status automations break |
| Slack integration | Linear notifications to Slack stop delivering |
| Webhooks | Downstream automations triggered by issue changes break |
| Notification delivery | In-app, email, and push notifications fail to arrive |
Match the check to the failure you need to catch
Follow supported Linear components for vendor-reported incidents. Add a public HTTPS check for your own website or API and define acceptable response codes, response time and body checks. A successful request is evidence about that endpoint, not proof that an entire customer journey works.
Use application logs and end-to-end tests for authenticated workflows, data correctness and transactions. Statusfield brings the monitoring results and vendor context together; it does not run a complete checkout or login flow.
Bring Linear updates to your team
Follow reported Linear status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Eligible first-time customers can start a free trial, no credit card required.
Follow Linear incidents with your team
Follow Linear and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Linear down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Linear incidents?
Follow reported Linear status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Linear status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.