Skip to main content
Klaviyo

Delays in real-time segmentation

Degraded Lasted 1h 23m · started · Klaviyo's page

Level
confirmed
Worst impact
Degraded
Components
Segments, Profiles
Down Index
19of 100

What to do

  • Check whether you use Klaviyo Segments, Profiles. 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 1h 23m it lasted.

    Anything that failed between 2026-08-19 17:15 UTC and 2026-08-19 18:38 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.

Updates from Klaviyo 3

  1. identified

    We are currently experiencing delays of up to approximately 3 hours in how quickly recent profile property updates are reflected in real-time segments. This means changes to profiles may take longer than usual to update segment membership, which can affect segment-based targeting. Email and SMS sending and other core functions are operating normally. We are actively working to resolve this and will share another update as soon as we have more information.

    provider

  2. monitoring

    A fix has been deployed and system performance is improving. Recent profile property updates are now being reflected in real-time segments more quickly, and the delay has improved to approximately 2.5 hours. Changes to profiles may still take slightly longer than usual to update segment membership as the system continues to catch up. Email and SMS sending and other core functions remain unaffected. We continue to monitor closely and appreciate your patience throughout this incident.

    provider

  3. resolved

    Profile property updates are now being reflected in real-time segments at normal speed. Any profile property changes made during the incident window have been reflected in segment membership as expected, and no action is required on your part. This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-203e0b3a7e

Is Klaviyo still down?

No, this incident was resolved 2026-08-19 18:38 UTC. For Klaviyo's live state, see https://down.guide/klaviyo.

How long did it last?

1h 23m, from 2026-08-19 17:15 UTC to 2026-08-19 18:38 UTC, by the times Klaviyo posted.

What was affected?

Klaviyo named Segments, Profiles.

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.