New Multi-region uptime checks and custom-domain status pages

Kayako Outage History

Daily provider-status observations and published incident history for Kayako.

Operational

Kayako is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Kayako for future changes.

98.2% of 57 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 30 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
Delayed or failed reply sending on US instances
major Observed active window 23h 34m

View incident details and source

Started:

US Pod
monitoring
Reply sending on US instances has been working normally since 02:43 UTC on October 14, and we continue to monitor. Replies that failed to send during the incident are not retried automatically; please resend any reply marked as failed. If you still see send failures, contact Support through the usual channels.
monitoring
Our infrastructure team has resolved the issue, and we don’t expect customers to experience further reply-sending failures. We’re closely monitoring the situation. Please contact Support through the usual channels if you continue to encounter problems.
identified
We’re aware that some customers hosted in our US region recently experienced intermittent failures when sending replies, updating conversations, and submitting Help Center requests, along with delays to email and other notifications. Our infrastructure team has mitigated the underlying issue and is working on a permanent fix. A small number of replies saved during this period may not have been delivered by email. Please check replies sent during the incident and resend any that your customer did not receive.

Legacy Incident Archive

1 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

June 2026
Elevated response times for ticket creation and reply actions
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The incident has been resolved, and we are monitoring the situation
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating reported slowness when creating or replying to tickets.