Is Kayako Down?

No — Kayako is up

Kayako's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 397 ms

Right now

The verdict is the worse of these two. How we decide

Kayako's status page

status.kayako.com · read 3 minutes ago · checked every 3 minutes

Operational

Kayako's components, as its status page reports them
Component	Status
Help Center	Operational
Agent portal	Operational
EU Pod	Operational
US Pod	Operational

Open their status page

FlareWarden checks

kayako.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 397 ms
Checked: 46 minutes ago

By region

Amsterdam reachable, 363 ms
Dallas reachable, 433 ms
Frankfurt reachable, 292 ms
Newark reachable, 264 ms
Paris reachable, 285 ms
Stockholm reachable, 546 ms
Sydney reachable, 519 ms
Toronto reachable, 474 ms

Timing by region

Connection timing for each region that loaded the page
Region	TCP	TLS	TTFB
Amsterdam	3 ms	13 ms	357 ms
Dallas	1 ms	10 ms	430 ms
Frankfurt	2 ms	10 ms	287 ms
Newark	2 ms	15 ms	256 ms
Paris	1 ms	14 ms	283 ms
Stockholm	16 ms	28 ms	523 ms
Sydney	1 ms	10 ms	516 ms
Toronto	1 ms	9 ms	470 ms

We check that kayako.com loads, not every feature behind it. Test it yourself

History

Incidents Kayako reported

Since Oct 22, 15 days · from status.kayako.com

Incidents: 1
Major or critical: 1
Median to resolve: 21h 42m

Kayako Service Disruption – Platform-Wide API and UI Failures
major · Oct 27
lasted 21h 42m

Kayako website availability

Measured by FlareWarden · kayako.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 501ms

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of kayako.com from multiple regions every 6 hours. Kayako's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 57 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Kayako itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Kayako goes down

We check Kayako every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required