Klaviyo: WhatsApp Disruption

What to do

Check whether you use Klaviyo WhatsApp Sending in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 5h 47m it lasted.
Anything that failed between 2026-06-06 17:18 UTC and 2026-06-06 23:05 UTC may need a replay.
Subscribe to Klaviyo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=klaviyo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

investigatingJun 6, 2026, 5:18 PM UTC
All WhatsApp functionality is currently unavailable for customers due to an upstream provider outage (including sending, integration setup and template editing). The Engineering team is actively investigating and will share more information as soon as it becomes available.
provider
resolvedJun 6, 2026, 11:05 PM UTC
The issue affecting WhatsApp features within Klaviyo has been resolved as of 6:45 PM US/Eastern on June 6, 2026. Our Engineering team has monitored performance and see that WhatsApp services have been restored including message sending, integration setup and template editing. This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Klaviyo still down?

No, this incident was resolved 2026-06-06 23:05 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.

How long did it last?

5h 47m, from 2026-06-06 17:18 UTC to 2026-06-06 23:05 UTC, by the times Klaviyo posted.

What was affected?

Klaviyo named WhatsApp Sending in us.

What caused it?

Klaviyo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Klaviyo's official status page, https://status.klaviyo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.