Incorrect segment membership impacted some users

Update timeline

1. identified Mar 21, 2026, 01:00 AM UTC

   Status: Identified Due to a network issue, a very small number of users experienced inconsistent segment membership. Affected customers may have noticed a minority of their users not matching expected segment criteria during this period. Our engineering team has identified the issue and repairing the affected users. Affected components Journeys (Degraded performance) Integrations (Operational) SMS (Operational) Push (Operational) Analytics & Reporting (Operational) Dashboard / UI (Operational) Email (Operational) APIs & SDK Endpoints (Operational) In-App Messages (Operational)

2. monitoring Mar 23, 2026, 10:00 PM UTC

   Status: Monitoring Majority of the users have been repaired for their segment membership and our engineering team continues to address the remaining users. Affected components In-App Messages (Operational) Email (Operational) SMS (Operational) Journeys (Degraded performance) Push (Operational) Analytics & Reporting (Operational) Dashboard / UI (Operational) Integrations (Operational) APIs & SDK Endpoints (Operational)

3. resolved Apr 01, 2026, 01:00 PM UTC

   Status: Resolved Our engineering team identified the issue internally and has completed the necessary mitigation and resolution steps. Affected components Analytics & Reporting (Operational) Dashboard / UI (Operational) SMS (Operational) In-App Messages (Operational) Push (Operational) Email (Operational) Integrations (Operational) APIs & SDK Endpoints (Operational) Journeys (Operational)