LiveChatChat widget performance degradation
Full widget performance was restored.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
Full widget performance was restored.
Resolved
On January 14, 2026, between 19:34 UTC and 21:36 UTC, the Webhooks service experienced a degradation that delayed delivery of some webhooks. During this window, a subset of webhook deliveries that encountered proxy tunnel errors on their initial delivery attempt were delayed by more than two minutes. The root cause was a recent code change that added additional retry attempts for this specific error condition, which increased delivery times for affected webhooks. Previously, webhook deliveries encountering this error would not have been delivered.<br /><br />The incident was mitigated by rolling back the change, restoring normal webhook delivery. <br /><br />As a corrective action, we will update our monitoring to measure the webhook delivery latency critical path, ensuring that incidents are accurately scoped to this workflow.
Resolved
We are investigating why our admin settings pages are currently unavailable. Please stand by.
Resolved
On January 15, 2026, between 16:40 UTC and 18:20 UTC, we observed increased latency and timeouts across Issues, Pull Requests, Notifications, Actions, Repositories, API, Account Login and Alive. An average 1.8% of combined web and API requests saw failure, peaking briefly at 10% early on. The majority of impact was observed for unauthenticated users, but authenticated users were impacted as well.<br /><br />This was caused by an infrastructure update to some of our data stores. Upgrading this infrastructure to a new major version resulted in unexpected resource contention, leading to distributed impact in the form of slow queries and increased timeouts across services that depend on these datasets. We mitigated this by rolling back to the previous stable version.<br /><br />We are working to improve our validation process for these types of upgrades to catch issues that only occur under high load before full release, improve detection time, and reduce mitigation times in the future.
Resolved
The issue has been completely resolved, and the requests with the v3 model are being processed.
Resolved
This incident has been resolved. Our cloud provider performed an unplanned cluster upgrade which caused downtime.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We’ve resolved the issue impacting our support intake. Following a surge of automated spam affecting our support workflows, we have chosen to disable our public support submission forms. Support remains readily available via our support email, team@elevenlabs.io. We are taking this step due to repeated spam-related disruptions and insufficient mitigation from our support platform provider. Please note that ElevenLabs services have not been affected in any way.
Resolved
A mitigation has been applied. If you are seeing erroneous user deletion events please reach out to our support team here: https://tailscale.com/contact/support.
Resolved
This incident has been resolved.
Resolved
This issue is now fully resolved.
Resolved
This incident has been resolved.
Resolved
The solution was delivered several minutes after the incident was reported, we were monitoring the performance of EU data center organizations and confirmed that it got back to normal
Resolved
Project creation success rate is back to normal
Resolved
We have identified the cause of the problem and publishing should now work as usual!
Resolved
The issue has been mitigated. We are not observing any further failures.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Earlier today our run trace data pipeline in one of our regional clusters experienced some issues with writing data. This pipeline asynchronously ingests run traces and statuses into our database. Runs were executing successfully, but the traces could not be ingested, resulting in outdated run statuses in the Inngest dashboard (stuck in 'queued'). These runs continued to be executed, but the dashboard observability is out of date and in some cases, incorrect. The system is fully operational now. We are analyzing our system's data to determine the most effective way to prevent this case in all parts of our system that rely on this and similar data pipelines.
Resolved
The incident affecting the broken redirection URL and affected links has been resolved. Some users were experiencing 404 errors when navigating from https://zapier.com/templates using the header links and dropdown menus. The affected services have returned to normal operation, and we have not observed ongoing customer impact since resolution. If you have any questions or need assistance, please don’t hesitate to reach out to our support team: https://zapier.com/app/get-help
Resolved
Tasks have returned to normal execution, and error rates are at normal levels.
Resolved
Between 12.45 PM PT and 4.00 PM PT users experienced service unavailability with Llama 3.3 70B, caused by a datacenter issue. We have deployed a fix and the issue is now resolved, model endpoint is operational.
Resolved
Database upgrade complete. We encountered some unexpected bugs after the upgrade which took some time to resolve.
Resolved
We experienced a degraded performance on our Payments products. You may have experienced delays in EUR Payments settlement. The service has recovered and payments are now settling in a timely manner. Impact start time: 18/01/2026, 23:11 UTC Impact end time: 18/01/2026, 23:54 UTC Client actions: None
Resolved
We've determined this is a bug for a small subset of requests and will look into a fix. Most users are not affected, please contact support if retries do not resolve.
Resolved
We've reduced the load on our deployment infrastructure and thus recovered.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors.
Resolved
This incident has now been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
All services are operating nominally.
Resolved
The fix has been running stable for 30 minutes and all system metrics are healthy. Run traces and metrics ingestion should be near realtime again.
Resolved
On Saturday, we experienced a brief incident where issue creation and issue state changes were unavailable for approximately 1 hour. This was caused by a problem in an internal maintenance process and the impact was limited to some US Hosted Linear workspaces. Additional controls have been put in place to prevent a recurrence and we apologize for the disruption caused.
Resolved
The incident is now resolved and the system is full operational. During this incident the system experienced a backlog in scheduling new runs and event data ingestion for the Inngest dashboard was delayed. The root cause was due to an issue with our internal event streams brokers which power internal event ingestion, run trace data ingestion and metrics ingestion. This caused delays in other data in the dashboard as well.
Resolved
This incident has been resolved.
Resolved
Everything is now resolved.
Resolved
E5-Mistral-7B-Instruct IS back in service
Resolved