Kayako Outage History

14 incidents recorded over the last 365 days, 4 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 Kayako status100.00% uptime history

Every Recorded Kayako Incident

Kayako incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Kayako Help Center and Agent Portal UnavailableBetween 17:23 and 18:55 UTC on October 28, Kayako help centers and the agent portal were unavailable for some customers. Pages returned an error stating that the instance did not exist or was experiencing temporary…-120 minResolved
Oct 27, 2026Kayako Service Disruption – Platform-Wide API and UI FailuresThis incident has been resolved. Kayako services have been operating normally since 22:40 UTC on October 2721h 42mResolved
Oct 24, 2026Scheduled Database Maintenance – Saturday 24 October 2026The scheduled maintenance has been completed.5h 0mScheduled
Oct 18, 2026Scheduled Database Maintenance – Sunday 18 October 2026The scheduled maintenance has been completed.4h 0mScheduled
Oct 14, 2026Delayed or failed reply sending on US instancesNo further occurrences of the issue have been observed since the fix was implemented over 24 hours ago. The issue is considered resolved, and we are closing this incident. If you experience any further issues, please…23h 32mResolved
Jul 26, 2026Scheduled Maintenance – Kubernetes Infrastructure UpgradeThe scheduled maintenance has been completed.6h 0mScheduled
Jul 26, 2026Kayako US Pod Scheduled Infrastructure MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 28, 2026Planned Infrastructure MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 2, 2026Elevated response times for ticket creation and reply actionsThe 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…7h 46mResolved
Mar 26, 2026Planned Infrastructure MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
Mar 21, 2026Scheduled System OptimizationThe scheduled maintenance has been completed.4h 0mScheduled
Feb 8, 2026Kayako CS RDS RestartThe scheduled maintenance has been completed.1h 0mScheduled
Jan 18, 2026Scheduled Maintentance of Kubernetes ClustersThe scheduled maintenance has been completed.6h 0mScheduled
Nov 23, 2025Planned Infrastructure MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled

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 Kayako 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 Kayako 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 Kayako 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 Kayako outage in this window ran 23h 32m, against a mean recovery of 7h 14m. If you depend on Kayako 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.