MoEngage incident

[DC-01] Lag in Periodic Segment Refresh

Minor Resolved View vendor source →

MoEngage experienced a minor incident on April 25, 2025 affecting In-app & On-site Messaging and Event Triggered Campaigns and Flows, lasting 4h 52m. The incident has been resolved; the full update timeline is below.

Started
Apr 25, 2025, 08:45 AM UTC
Resolved
Apr 25, 2025, 01:37 PM UTC
Duration
4h 52m
Detected by Pingoru
Apr 25, 2025, 08:45 AM UTC

Affected components

In-app & On-site MessagingEvent Triggered Campaigns and Flows

Update timeline

  1. identified Apr 25, 2025, 08:45 AM UTC

    Hi, We are currently addressing a delay in the Periodic Segment Refresh on DC-01 This situation affects trigger-based campaigns, Flows, and Inbound Campaigns (In-App, OSM), as they are operating with outdated segments. However, rest assured that real-time campaigns, one-time campaigns, and dashboard segmentation queries are functioning normally. Our team is actively working to resolve this issue promptly. We appreciate your patience and cooperation during this time. We will keep updating the progress and try to resolve this soon. If you have any questions, please don't hesitate to reach out to our support team. Thank you, Team MoEngage

  2. identified Apr 25, 2025, 11:09 AM UTC

    The team has made progress to scale our infrastructure to burn the lag. The current lag will take another 2-3 hours to clear.

  3. monitoring Apr 25, 2025, 12:47 PM UTC

    The lag has been cleared. Services are back to normal. We are monitoring our systems.

  4. monitoring Apr 25, 2025, 12:48 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Apr 25, 2025, 01:37 PM UTC

    The issue has been resolved. All the services are operational and continue to be monitored closely. We will work on the post-mortem and take corrective actions to avoid such issue in the future.

  6. resolved Apr 25, 2025, 01:37 PM UTC

    This incident has been resolved.