LiveChat Outage History

30 incidents recorded over the last 365 days, 29 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live LiveChat status100.00% uptime history

Every Recorded LiveChat Incident

LiveChat incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 15, 2026Scheduled maintenanceMaintenance has started32 minResolved
Oct 14, 2026Workflows malfunctionThe issue with Workflows has been resolved, and services are now operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding.1h 51mResolved
Oct 12, 2026Workflows malfunctionThe issue with Workflows has been resolved, and services are now operating normally. We apologize for any disruption this may have caused and appreciate your patience and understanding.7h 38mResolved
Sep 30, 2026Scheduled maintenanceWe will be performing platform maintenance affecting both the US and EU data centers on September 30th from 2:30 AM to 2:40 AM (ETD). During this ten-minute maintenance window, some agents may experience brief errors…10 minScheduled
Sep 26, 2026Login issuesThe issue has been resolved, and services are operating normally. No further impact is expected.57 minResolved
Jul 28, 2026Issues with opening filesThe issue with opening files has been resolved, and services are operating normally. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.25h 34mResolved
Jul 10, 2026Workflow degraded performanceThe issue has been resolved, and we can confirm that services are operating normally again.16 minResolved
Jun 12, 2026Workflow degraded performanceThe issue has been resolved, and we can confirm that services are operating normally again.1h 5mResolved
May 25, 2026LiveChat - Issues with reports from Export Raw DataThe issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.44 minResolved
May 19, 2026Workflows delayThe issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding.2h 4mResolved
May 13, 2026Issues with adding new Knowledge SourcesThe issue has been resolved, and services are operating normally. No further impact is expected.32 minResolved
Feb 25, 2026LiveChat - outageA fix has been implemented, and we see that our assets become available and reports a healthy status. We’ve been monitoring the situation, and will continue checks29h 46mResolved
Feb 21, 2026Messages sent via the chat widget are delayedThe incident has been resolved and services are now operating as expected. We will continue to monitor the situation, but no further impact is anticipated.31 minResolved
Feb 10, 2026Messages sent in the chat widget may be delayedThis incident has been resolved and services are operating normally. Thank you for your patience.1h 6mResolved
Jan 20, 2026Performance degradation of our servicesWe see that the issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that the infrastructure is healthy, and we are not seeing further errors. Throughout the degradation, our platform…2h 14mResolved
Jan 20, 2026Performance degradation of our servicesThe issue within our cloud provider’s infrastructure has been mitigated, and we can confirm that all affected resources have been fully restored. Our platform has remained available throughout, thanks to built-in…4h 12mResolved
Jan 20, 2026Chat widget not working on Text websitesCommunication is fully restored now.17 minResolved
Jan 20, 2026Chat widget performance degradationFull widget performance was restored.17 minResolved
Jan 13, 2026Some users might not be able to access the LiveChat appThe fix has been implemented and the issue has been resolved.8 minResolved
Dec 22, 2025Web application - degraded performance[03:11am] LiveChat is now back up and running again! We are investigating the issue - thanks for your patience :) [02:59 am] We're experiencing some downtime. Service may be interrupted.-5682234 minResolved
Dec 22, 2025Connection issuesErrors have been fully resolved. Please contact us if you notice any further issues.-5419661 minResolved
Dec 22, 2025Chats dropThis incident has been resolved.-5451575 minResolved
Dec 22, 2025Connection issuesPermanent fix for such issues is now live. We've struggled with connection issues caused by memory overload.-5543646 minResolved
Dec 22, 2025Login problemsThis problem has been resolved. Please reach us through support@livechatinc.com if you have any issues-5585776 minResolved
Dec 22, 2025Database problems[08:36pm] Service is back and fully functional. Thanks for your patience. [06:19pm] Still working on the database problem. It might take up to 2 hours. We will keep you posted on that. [01:24pm] There might be a small…-5680793 minResolved
Dec 22, 2025DDoS attackProblem with DDoS attack has been resolved.-5286092 minResolved
Dec 22, 2025DDoS attackProblem with DDoS attack has been resolved.-5290363 minResolved
Dec 22, 2025Connection issuesThe issue has been resolved.-5347574 minResolved
Dec 22, 2025DNS issueThe DNS issue has been resolved.-5377992 minResolved
Dec 22, 2025DDoS attackAll earlier problems are solved now. If you are still experiencing any problems please contact us at support@livechatinc.com-5410870 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next LiveChat incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This LiveChat Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before LiveChat acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single LiveChat outage in this window ran 1d 5h, against a mean recovery of 4h 12m. If you depend on LiveChat in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.