# Issue with Engage UI

- Provider: [Segment](https://down.guide/providers/segment)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 4h 11m
- started 2026-09-03 18:30 UTC
- Web Interface (US), Engage (US)
- us
- id: DWN-3ddc5b5d1c
- Official page: https://stspg.io/8q4vs0j2vjd0

## Updates from Segment
### 2026-09-03 17:53 UTC: identified
We have identified an issue affecting the page load of Engage UI including Audiences and Journeys.

### 2026-09-03 18:06 UTC: identified
We are continuing to work on a fix for this issue.

### 2026-09-03 18:30 UTC: identified
We are continuing to take urgent action to fix this issue.

### 2026-09-03 18:56 UTC: identified
We are continuing to take urgent action to fix this issue.

### 2026-09-03 19:34 UTC: identified
We are continuing to take urgent action to fix this issue.

### 2026-09-03 20:26 UTC: monitoring
A fix has been applied and the Engage UI experience should be fully functional. We are continuing to monitor results.

### 2026-09-03 22:41 UTC: resolved
This incident has been resolved.

From the builder: does your app depend on Segment? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=segment) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Segment.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-3ddc5b5d1c), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.