Kayako Outage History

Kayako is up right now

Kayako had 2 outages in the last 2 years totaling 22h 55m of downtime — averaging 0.1 incidents per month.

There were 2 Kayako outages since October 20, 2025 totaling 22h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.kayako.com

Minor June 2, 2026

Elevated response times for ticket creation and reply actions

Detected by Pingoru
Jun 02, 2026, 03:41 PM UTC
Resolved
Jun 02, 2026, 11:28 PM UTC
Duration
7h 46m
Affected: Help CenterAgent portal
Timeline · 4 updates
  1. investigating Jun 02, 2026, 03:41 PM UTC

    We are currently investigating reported slowness when creating or replying to tickets.

  2. investigating Jun 02, 2026, 03:43 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 02, 2026, 08:56 PM UTC

    The incident has been resolved, and we are monitoring the situation

  4. resolved Jun 02, 2026, 11:28 PM UTC

    The issue causing elevated response times for ticket creation and reply actions has been resolved. Our Infrastructure team has completed the necessary mitigation steps, and we are seeing response times return to expected levels. We will continue to monitor the platform to ensure stability. Thank you for your patience while we worked through this issue.

Read the full incident report →

Critical October 20, 2025

AWS Degraded – Multiple Services in US-East-1 Region

Detected by Pingoru
Oct 20, 2025, 08:08 AM UTC
Resolved
Oct 20, 2025, 11:16 PM UTC
Duration
15h 8m
Affected: Help CenterAgent portalEU PodUS Pod
Timeline · 2 updates
  1. identified Oct 20, 2025, 08:08 AM UTC

    AWS has confirmed “increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region” with a severity labelled “Degraded”. This affects Kayako instances and you may experience issues loading your Help Centers or interacting with the Help Center.

  2. resolved Oct 20, 2025, 11:16 PM UTC

    AWS has confirmed that the outage in the US-EAST-1 region has now been resolved, and all services are operational.

Read the full incident report →