Skip to main content
Kayako logo

Is Kayako Down?

No — Kayako is up

Reachable from all 8 checked regions

Average response time: 511ms

Last checked · checks run every 6 hours

Official status page: https://status.kayako.com

Kayako uptime

99.54%
Last 7 days
99.70%
Last 30 days
99.70%
Last 90 days
450ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 11 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

6-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: no data
Sep 9: no data
Sep 10: 100.00% uptime, 16 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 96.88% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 44 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
446ms
DNS 0ms TCP 2ms TLS 17ms TTFB 434ms
arn
607ms
DNS 0ms TCP 1ms TLS 14ms TTFB 595ms
bom
831ms
DNS 0ms TCP 2ms TLS 15ms TTFB 819ms
cdg
277ms
DNS 2ms TCP 1ms TLS 13ms TTFB 266ms
sin
843ms
DNS 1ms TCP 1ms TLS 18ms TTFB 832ms
sjc
358ms
DNS 0ms TCP 3ms TLS 16ms TTFB 344ms
syd
399ms
DNS 0ms TCP 1ms TLS 11ms TTFB 390ms
yyz
331ms
DNS 3ms TCP 1ms TLS 12ms TTFB 322ms

What Kayako does

Kayako is help desk software that gives support teams a shared inbox for customer conversations across email, chat and social channels, alongside a self-service help centre. Companies use it as the queue their customers reach when something goes wrong, which makes an outage here the moment a business loses contact with the people already having a problem.

What an outage looks like

Agents cannot sign in to the agent portal or see the ticket queue, so conversations pile up unanswered with no visible sign to the customer. Separately, the customer-facing help centre can fail to load, leaving self-service articles unreachable while agents work normally. New tickets may not appear, and replies can fail to send even when the interface accepts them.

What to do about it

Read status.kayako.com, which reports Help Center, Agent portal, EU Pod and US Pod as its four components. Find your pod first, because the two are separate and a colleague on the other one is not evidence about yours. If only Help Center is affected, agents can still work and the gap is customer self-service, so consider posting the alternative contact route somewhere customers will see it.

Is it down for everyone, or just you?

If this page says Kayako is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Zendesk
Zendesk
Intercom
Intercom
Help Scout
Help Scout
Gorgias
Gorgias

Kayako outage FAQ

My colleague can sign in and I cannot. Is Kayako down?
Possibly, and the pod split is the first thing to check. Kayako reports EU Pod and US Pod as separate components, so an incident can affect one region's accounts while the other continues normally. A colleague signing in successfully proves nothing unless they are on the same pod as you. Confirm which pod your account uses before you start resetting passwords or clearing sessions.
Will customer emails sent during a Kayako outage be lost?
Incoming mail to a help desk is normally queued by the sending mail server and retried, so messages sent during an incident commonly arrive once the service recovers rather than disappearing. Kayako does not publish retry behaviour for every channel, so treat delayed arrival as likely and complete loss as possible. Watch for a burst of backdated tickets on recovery and sort by original send time rather than arrival.
Is it Kayako or my own email or chat integration?
Compare scope. A broken mail forwarding rule, an expired channel connection or a changed DNS record affects one inbox or one channel while the rest of the queue keeps moving. A Kayako incident affects every agent on your pod at once. Check the status page before you start reconnecting channels, since reconnecting during an incident can leave settings in a state you then have to unpick.
Can I still help customers while Kayako is down?
Usually yes, by falling back to the underlying channel. Mail sent to your support address continues to be handled by your mail provider and can be read there directly, and phone or social channels are unaffected by a help desk incident. Note which conversations you handled outside the system so they can be recorded afterwards, because those replies will not appear in the ticket history on their own.
The help centre is down but agents are fine. What should we do first?
Tell customers where to go instead. Help Center is a separate component from the Agent portal, so self-service articles can be unreachable while your team is fully able to answer. The practical risk is customers assuming support is unavailable and giving up rather than contacting you. Publishing the direct contact route on a channel you control turns a self-service outage into a busier queue instead of silence.

How we measure this

  • We request Kayako's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Kayako publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Kayako goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required