Skip to main content
Segment

Issue with Engage UI

Partial outage Lasted 4h 11m · started · Segment's page

Level
confirmed
Worst impact
Partial outage
Components
Web Interface (US), Engage (US)
Regions
us
Down Index
35of 100

What to do

  • Check whether you use Segment Web Interface (US), Engage (US) 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 4h 11m it lasted.

    Anything that failed between 2026-09-03 18:30 UTC and 2026-09-03 22:41 UTC may need a replay.
  • Subscribe to Segment's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=segment works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Segment 7

  1. identified

    We have identified an issue affecting the page load of Engage UI including Audiences and Journeys.

    provider

  2. identified

    We are continuing to work on a fix for this issue.

    provider

  3. identified

    We are continuing to take urgent action to fix this issue.

    provider

  4. identified

    We are continuing to take urgent action to fix this issue.

    provider

  5. identified

    We are continuing to take urgent action to fix this issue.

    provider

  6. monitoring

    A fix has been applied and the Engage UI experience should be fully functional. We are continuing to monitor results.

    provider

  7. resolved

    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-3ddc5b5d1c

Is Segment still down?

No, this incident was resolved 2026-09-03 22:41 UTC. For Segment's live state, see https://down.guide/segment.

How long did it last?

4h 11m, from 2026-09-03 18:30 UTC to 2026-09-03 22:41 UTC, by the times Segment posted.

What was affected?

Segment named Web Interface (US), Engage (US) in us.

What caused it?

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

Where does this come from?

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