BufferBuffer Stuck Loading
After monitoring for stability, we're confident this issue is resolved!
Resolved
Outages and recoveries from the services you depend on.
40 incidents
After monitoring for stability, we're confident this issue is resolved!
Resolved
The issue has been resolved following a deployment. system table queries and the MCP have returned to normal operation.
Resolved
We've fully caught up and process LLM as a judge in realtime again.
Resolved
This incident has been resolved.
Resolved
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 support@linear.app "support@linear.app": mailto:support@linear.app.
Resolved
This issue is now resolved for all users. Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users globally. Previous impact to end users: Slack users experienced difficulties accessing Slack features, including Messaging, Workflows, Apps, Integrations, APIs, Canvas, and Connections, beginning at 22:21 UTC on May 27, 2026. Following an infrastructure change, a cascading scheduling failure caused widespread service impact across all regions and clients. Slack services largely returned to normal operational levels at 05:45 UTC on May 27, with residual impact that remained during the deployment. A brief issue with Canvas surfaced at 10:00 UTC on May 28 that lasted until approximately 12:30 UTC. Required resolution steps: No steps required. We apologize for any disruptions to your day. We'll undertake a full investigation of the incident, establishing the technical trigger, the mechanism of failure, and preventative measures to avoid further disruptions.
Resolved
EAS Submit jobs of certain types have not been getting their status and logs updated in website, despite having been processed successfully. We have identified the issue, implemented a fix and have just finished updating all the old records to their right state.
Resolved
On May 19, 2026, between 05:30 UTC and 14:50 UTC, some Copilot users experienced failures when using code completions, chat sessions, and cloud agent sessions. At peak impact, approximately 13% of Copilot API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC. The incident was caused by rate limits being exceeded on a shared infrastructure component. A recently enabled feature increased call volume to this component, and the combined load exceeded capacity limits as traffic increased during business hours. We mitigated the incident by deploying a caching layer to reduce load on shared infrastructure. To prevent recurrence, we are separating rate limit scopes between services, adding monitoring for internal dependency rate limiting, and reducing redundant calls.
Resolved
The issue has been resolved
Resolved
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 support@linear.app if you experience any problems with email intake after this time.
Resolved
This incident has been resolved.
Resolved
The incident was resolved.
Resolved
Their outage has been resolved
Resolved
We think the impact from the issue is over.
Resolved
The issue has been fully resolved. Everything should be back to normal.
Resolved
Resolved - Some users were unable to complete subscriptions on web and mobile. Affected users may have experienced the Subscribe button becoming unresponsive or encountered the error message submit_error_source:email during checkout.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
## Service Impact A subset of customers experienced elevated latency in notification delivery. ## Incident Summary While migrating a subset of our background processing services to Amazon EKS, we encountered an issue with delivery of internal metrics. The discovered issue did not impact performance or availability, but would have impaired our ability to detect such problems if they occurred. Out of an abundance of caution we decided to revert the migration, and moved those services back to the original infrastructure on AWS Fargate. When migrating to EKS, we scale down and disable automatic scaling on Fargate. This allows us to quickly migrate back by scaling up Fargate. When we moved the workloads back to Fargate to restore internal metrics, we missed the step to re-enable autoscaling. As a result, the affected services did not have sufficient capacity and could not keep up with incoming work. We re-enabled autoscaling promptly once the problem was discovered, and provisioned extra capacity for customers where a backlog of work had accumulated. Between 09:17 and 10:17 UTC, a small subset of our customers were impacted. Individual customers experienced a limited outage of notification services, which lasted between 35 and 58 minutes within this window, if there was any impact at all. The migration is performed in small batches, so not all customers experienced this incident. ## Changes we're making * We are simplifying the runbook used to rollback migrations in the event of incidents. * We are adding more verification steps to the migration process.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue causing elevated application latency has been resolved. We have confirmed that system performance has returned to normal levels and continue to monitor closely to ensure ongoing stability.
Resolved
This incident has been resolved.
Resolved
Processes are continuing to work normally, and all affected accounts have been fixed, so we are not moving this issue to resolved.
Resolved
The issue has been resolved, and exports should now be working as expected.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
This issue is now resolved.
Resolved
Our billing provider has corrected the problem, and all subscription updates are processing normally and without delay.
Resolved
Some users may have been unable to log in to ClickHouse Agents due to an overly broad login rate limit. A configuration change was rolled out, access has been confirmed restored, and no customer data or ClickHouse services were impacted.
Resolved
We have scaled our infra to drain the queue backlog. Evals are executed without delay again.
Resolved
Meta's engineers have confirmed that the issue with Instagram's API has been fully resolved, and we're happy to confirm that we're seeing publishing rates back to normal levels. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
We can confirm the issue has been resolved.
Resolved
Some customers in AWS us-east-1 may observe a small number of gRPC UNIMPLEMENTED errors returned during the time period 15:00-15:30:00 UTC. This issue was investigated and identified as being related to a deployment in the affected region that has been rolled back - no further impact is expected.
Resolved
This issue is now resolved.
Resolved
No further issues have been observed and this incident is now considered resolved.
Resolved
**What happened:** During a planned migration process, we hit a scaling limit on a core infrastructure component which impacted certain customer traffic. **Impact:** A portion of customer traffic was dropped causing a full outage for customers on Silos 7, 8, and 9. **Fix:** The migration was rolled back in all customer environments. **Prevention:** The migration has not been reapplied and is on hold, pending further investigation by the team to establish a safe migration path.
Resolved
This incident has been resolved, and builds have returned to functioning normally.
Resolved
We can confirm the issue has been fully resolved.
Resolved