LiveAgent Outage History

LiveAgent is up right now

Pingoru has recorded 15 incidents for LiveAgent: 5 in the last 12 months and 1 in the last 90 days.

Source: status.liveagent.com

15incidents recorded
5last 12 months
1last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking LiveAgent in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202610 of 744 (0%)
June 202620 of 720 (0%)
July 202610 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202610 of 744 (0%)
November 202600 of 141 (0%)

Incidents, newest first

Minor October 21, 2026 PHP vulnerabilities CVE-2026-109618 / CVE-2026-109619 (PHP2Shell) –

Started Oct 21, 2026, 02:00 PM UTC· resolved Oct 21, 2026, 02:00 PM UTC

  1. investigating Oct 21, 2026, 02:00 PM UTC

    PHP vulnerabilities CVE-2026-109618 / CVE-2026-109619 (PHP2Shell)

Read the full incident report →

Major July 24, 2026 Outage in Singapore data center –

Started Jul 24, 2026, 12:35 PM UTC· resolved Jul 24, 2026, 12:35 PM UTC

  1. investigating Jul 24, 2026, 12:35 PM UTC

    Outage in Singapore data center

Read the full incident report →

Minor June 28, 2026 Admin tickets and emails in ec1 –

Started Jun 28, 2026, 10:59 AM UTC· resolved Jun 28, 2026, 10:59 AM UTC

  1. investigating Jun 28, 2026, 10:59 AM UTC

    Admin tickets and emails in ec1

Read the full incident report →

Minor June 23, 2026 Service degradation on EU and US accounts –

Started Jun 23, 2026, 03:36 PM UTC· resolved Jun 23, 2026, 03:36 PM UTC

  1. monitoring Jun 23, 2026, 12:00 AM UTC

    layout: post title: Service degradation in ue1 status: resolved severity: degradation date: 2026-06-23 20:40 UTC resolvedDate: 2026-06-23 21:41 UTC clusters: [ue1] services: [all] incident_states: status: investigating content: ‘We are currently experiencing service degradation affecting all services in the ue1 region. Users may encounter slower responses or intermittent issues while using the platform. Our server administration team is actively investigating and working to resolve the issue, and further updates will follow as more information becomes available.’ status: resolved content: “We are pleased to inform you that the recent degradation has been successfully resolved, and all affected services have been fully restored. Our infrastructure administrators will remain monitoring the situation further. We sincerely apologize for any inconvenience this degradation may have caused and appreciate your patience and understanding.”

  2. investigating Jun 23, 2026, 03:36 PM UTC

    Service degradation on EU and US accounts

Read the full incident report →

Minor May 6, 2026 Agent panel slowness in Europe data center –

Started May 06, 2026, 05:40 AM UTC· resolved May 06, 2026, 05:40 AM UTC

  1. investigating May 06, 2026, 05:40 AM UTC

    Agent panel slowness in Europe data center

Read the full incident report →

Minor October 20, 2025 Connectivity degradation related to problems on AWS side –

Started Oct 20, 2025, 03:00 PM UTC· resolved Oct 20, 2025, 03:00 PM UTC

  1. investigating Oct 20, 2025, 03:00 PM UTC

    Connectivity degradation related to problems on AWS side

Read the full incident report →

Minor October 20, 2025 Connectivity degradation in U.S. data center –

Started Oct 20, 2025, 07:19 AM UTC· resolved Oct 20, 2025, 07:19 AM UTC

  1. investigating Oct 20, 2025, 07:19 AM UTC

    Connectivity degradation in U.S. data center

Read the full incident report →

Minor October 20, 2025 Performance degradation related to problems on AWS side –

Started Oct 20, 2025, 07:19 AM UTC· resolved Oct 20, 2025, 07:19 AM UTC

  1. investigating Oct 20, 2025, 07:19 AM UTC

    Performance degradation related to problems on AWS side

Read the full incident report →

Major May 13, 2025 Live chat support unavailable –

Started May 13, 2025, 11:00 AM UTC· resolved May 13, 2025, 11:00 AM UTC

  1. investigating May 13, 2025, 11:00 AM UTC

    Live chat support unavailable

Read the full incident report →

Major April 25, 2025 Outage in EU - Frankfurt data center –

Started Apr 25, 2025, 11:00 AM UTC· resolved Apr 25, 2025, 11:00 AM UTC

  1. investigating Apr 25, 2025, 11:00 AM UTC

    Outage in EU - Frankfurt data center

Read the full incident report →

Minor April 16, 2025 Issue with incoming mail accounts of type Forwarding leading to SPAM misclassification 527d 1h

Started Apr 16, 2025, 01:58 PM UTC· resolved Sep 25, 2026, 03:40 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 8, 2025 Call center feature unavailability in EU datacenter 563d 11h

Started Feb 08, 2025, 10:20 AM UTC· resolved Aug 25, 2026, 09:58 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major January 24, 2025 Call center outage in EU - Frankfurt data center 524d 9h

Started Jan 24, 2025, 09:50 AM UTC· resolved Jul 02, 2026, 07:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major January 23, 2025 Callcenter outage in clustersUS - North Virginia 525d 18h

Started Jan 23, 2025, 01:24 AM UTC· resolved Jul 02, 2026, 07:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor December 12, 2024 Unavailable LiveAgent support 519d 3h

Started Dec 12, 2024, 08:44 AM UTC· resolved May 15, 2026, 12:27 PM UTC

  1. monitoring Dec 12, 2024, 08:44 AM UTC

    Our support team instance is currently experiencing an unexpected issue due to which our support services might be degraded or unavailable. Our developers are already working on a solution, we expect to have our chat support available again within approximately 45 minutes. We will keep updating our status page as soon as there is any new info. We apologize to all customers who would like to reach our support team. Update The issues were resolved and our support team is fully available again.

Read the full incident report →