28 Linear incidents · mars 2026 — official updates, affected components, duration and resolution details.
Les docs linéaires sont actuellement incapables de charger, nous sommes en train de faire un changement pour corriger cela dès que possible.
Documentation site now loads after refreshing.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Some users are unable to start Codex sessions from Linear. We’re investigating and working with the integration provider to resolve the issue.
Certains clients éprouvent des problèmes avec le chargement linéaire. Nous enquêtons - excuses pour le désagrément.
Certains clients de la région américaine éprouvent encore des problèmes avec le chargement linéaire. Nous avons fait reculer un changement récent et continuons d'atténuer le problème, mais certains utilisateurs touchés pourraient encore rencontrer des problèmes. Nous allons partager une autre mise à jour sous peu.
Nous constatons des améliorations après les mises à jour et continuons de surveiller la stabilité.
Des déploiements récents ont ajouté une charge supplémentaire à nos bases de données, et une correction a été mise en place. Merci de votre patience pendant que nous avons travaillé pour résoudre cela.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Some users in India may be experiencing difficulties loading Linear in the web and desktop apps. We are investigating the issue and working to mitigate it.
We identified regional networking issues from an upstream provider affecting some users in India, which may prevent Linear from loading. We’re continuing to monitor the situation and will share further updates as we learn more.
An upstream regional networking issue impacted access for some Linear users in India. The issue has now been resolved, and our service is operating normally for all regions.
We have had reports of Linear not loading for some users. We are investigating and will be back with further updates as soon as possible.
We are continuing to investigate to narrow down the root cause. We apologise for the inconvenience this is causing, thank you for your continued patience.
Our team is still actively investigating. We'll provide a further update by 17:45 UTC - thank you for your continued patience.
We are seeing improvements after updates, and users are now able to load and sync in Linear again. We are continuing to monitor improvements.
Some customers were experiencing issues with Linear loading and syncing. Performance has returned to normal, and the issue is resolved. We appreciate your patience while we worked on this.
Some users with EU-hosted workspaces may be experiencing delays syncing changes. Service is recovering, and we are monitoring performance.
Some users with EU-hosted workspaces experienced delays syncing changes for a short period of time this morning. Sync performance has returned to normal, and the issue is resolved. Thank you for your patience while we worked on this.
We're investigating reports of general latency when taking actions in Linear — we're working to confirm the suspected root cause and remediate the degradation. We'll provide updates as we have them.
We’ve rolled back a recent change that may have contributed to the slowdown and performance is improving. We’re keeping a close eye on continued recovery.
The increased latency has been resolved, and Linear should be operating normally again. We rolled back the query change that caused the slowdown and have confirmed performance has recovered.
Some users may be experiencing errors when loading code diffs in Linear. We are investigating and will share an update as soon as we have more information.
We identified the cause of errors when navigating to _Reviews_ and reverted the impacting change. Reported errors are stabilizing, and affected users should see recovery after refreshing Linear. We are monitoring to ensure continued stability.
The revert resolved broader errors affecting navigation to the Reviews tab. However, a smaller subset of errors continues when opening specific pull requests. We are investigating these remaining cases and monitoring recovery as we work toward full resolution.
We identified and addressed the remaining cause of errors affecting specific pull requests. The Reviews experience is now functioning normally, and any remaining affected users should see recovery after refreshing Linear. We’re monitoring for continued stability before fully resolving the incident.
This issue has been resolved, and the Reviews experience is functioning normally — thank you for your patience. If you continue to see any trouble, please reach out to [email protected] and we'll take a look!
Some users may be experiencing delays when using automations, including the Linear Agent and Asks. We are investigating and will provide updates as more information becomes available.
Some users in our US and European regions continue to experience delayed responses from Linear Agent and some other automations including Asks. We have increased service capacity and are continuing to work towards restoring normal response times.
Agent responses and other delayed workflows should now be operating normally. We’re continuing to monitor performance to ensure recovery remains stable.
Processing continues to operate normally, and we have not observed further errors. We’re continuing to monitor performance to ensure the recovery remains stable.
The delays affecting agent responses and other workflows have been resolved. We're sorry for the disruption.
We're investigating a problem with the right-click/context menu on issues. Command menu or keyboard shortcuts are functional as a workaround in the meantime. We'll keep our status site updated with news as we work towards a fix.
We've identified the problem and deployed a fix. You may need to refresh (⌘+R / CTRL+R) to get the latest changes.
Linear is currently unavailable for many users across the web and desktop apps. We are investigating a partial outage, and will post an update shortly.
Linear should now be available again. We’re monitoring recovery to ensure service remains stable.
This incident has been resolved, and Linear is operating normally across all regions. We rolled back the affected services and have confirmed that error rates remain normal. We apologize for the disruption.
We’re currently investigating an issue affecting the in-app contact form. In the meantime, if you need to reach our support team, please contact us directly at [[email protected]](mailto:[email protected] "[email protected]"). We’ll share another update as soon as we have more information.
The problem with in-app submissions is still being worked on, we've isolated the problem and it should be restored soon.
We've confirmed that new submissions through our in-app contact form are being received successfully again. We're continuing to process and review messages that were impacted and will follow up with affected customers as quickly as possible. Thank you for your patience while we complete this work. We'll provide a further update once recovery of all delayed messages has been completed.
We've resolved the issue affecting submissions through our in-app contact form, and new support requests are being received successfully again. Our team will continue reviewing and replying to delayed support requests as quickly as possible. We apologize for the delay and appreciate your patience.
Due to an upstream provider outage, code intelligence requests through the Linear Agent are currently failing to process. We'll continue to observe the situation and once the upstream issue is resolved we'll resolve our status.
Normal functionality has resumed to the Linear Agent's coding intelligence features.
We’re investigating delays affecting event processing for some workspaces hosted in our US region. This may cause updates in Linear to appear delayed or out of date. We’re actively working on a fix and will share another update as soon as we have more information.
We’ve implemented a fix for delays affecting updates for some workspaces hosted in our US region, and processing has resumed. Some users may still see delayed or out-of-date information while the remaining backlog clears. We’re continuing to monitor recovery closely.
We’ve resolved the delays that were affecting updates for some workspaces hosted in our US region, and service should now be operating normally. We hit an unexpected condition in our event processing that caused the system to back up. If you still see stale information in Linear, please refresh and try again. We are working on a fix to prevent future occurrences, and thank you for your patience while we worked on this.
We’re investigating an issue causing Linear to fail to load for some users. You may see a network error while opening the app while this is ongoing. We’re working on mitigation and will share another update as soon as we have more information.
We’re continuing to investigate an issue causing Linear to fail to load for some users. You may see a network error when opening the app while this incident is ongoing. We will share another update as soon as we have more information and we're sorry for the difficulty in the meantime.
This incident has now been resolved and Linear should now be loading normally again for all users. We identified an error with DDOS protection rules being applied in error, and applied mitigation changes to prevent this from affecting user logins. If you still run into problems accessing Linear after a refresh, please reach out to [[email protected]](mailto:[email protected] "[email protected]").
We’re investigating an issue causing email intake for Linear Asks to fail. Emails sent to intake addresses may bounce, and new issues may not be created from Asks intake emails while we work on mitigation. We’ll share another update as soon as we have more information.
We’re continuing to investigate an issue affecting Linear Asks email intake. Emails sent to intake addresses may bounce, and new asks will not be created from email while this is ongoing. We are working to restore email intake functionality and will continue share updates as they become available.
Asks email intake has been restored and is working again. We identified the issue and implemented a fix, and have confirmed the flow is working again end to end. Please reach out to [email protected] if you experience any problems with email intake after this time.
Task processing in our EU region was briefly delayed from 12:45 to 13:05 UTC after capacity scaled down too far, which slowed some background actions from completing normally. We scaled capacity back up and processing has recovered. Service should now be operating normally.
Earlier today, some US customers may have seen degraded or incomplete search results for a number of hours. This issue has now been resolved, and search should be working normally again. The impact was caused by backed-up event processing, which has since been cleared. We’re sorry for the disruption and are continuing follow-up work to help prevent similar issues.
We’re investigating delays in background processing. This may affect things like notifications, emails, webhooks, automations, and some integrations. We’re working to identify the cause and mitigate the issue, though are seeing early signs of stabilization.
We identified failures with our event processing and our backlog of events has returned to regular levels and delays are no longer significant. We're continuing to monitor for stability.
We mitigated the issue causing delays in background event processing, and the backlog has returned to regular levels. Systems are operating normally — you should no longer experience issues with notification or email delivery, webhooks, or other event-driven updates. Please reach out to [[email protected]](mailto:[email protected] "[email protected]") if you continue to experience any related problems.
We've monitoring further delays in background activity that have affected some users in recent days. While most of the service is operating normally, some notifications and updates may still be delayed as recovery continues for affected users. We’re seeing improvement and will share another update soon.
We're continuing to work through a backlog of delayed background activity affecting some users. This includes delays to email and Slack notifications as well as webhooks. We've scaled up our infrastructure to process the backlog more quickly and are actively monitoring progress. Notifications affected by this backlog should come through in the coming hours and we'll share another update once the backlog has cleared.
We’ve identified the cause of the delays affecting background activity for some users, including notifications, webhooks, and other asynchronous updates. We’re actively applying remediation to reduce pressure on our task processing system and restore normal performance. We’ll share another update as soon as we have more to report.
We’ve addressed the issue that was causing delays in background task processing earlier today, and task activity has been operating normally again for the past few hours. A remaining search indexing backlog means some recent changes may still take a few more hours to appear in search results. This does not affect task processing, notifications, webhooks, or other asynchronous updates. We’re continuing to monitor recovery and will share another update once search indexing has fully caught up.
We’ve resolved the issue that caused delays in background task processing and search indexing. Systems are now operating normally again. Recent changes should appear as expected in search, and you should no longer experience delays with notifications, webhooks, automations, or other event-driven updates. Please contact [[email protected]](mailto:[email protected]) if you continue to see related issues.
From approximately 21:15 to 21:20 UTC, customers using cycles may have seen errors in Linear. This was caused by unintended side effects from an internal migration related to ongoing performance and technical-debt improvements. Our team identified the issue quickly, rolled back the change and service has recovered. We're continuing to monitor stability.
As noted, an internal migration related to ongoing performance and tech-debt improvements caused errors affecting customers using cycles. Our team identified and reverted the issue quickly, and service has now fully recovered. We appreciate your patience as we worked to resolve things!