CrossEngage incident

Data Processing Delay

Minor Resolved View vendor source →

CrossEngage experienced a minor incident on April 30, 2024 affecting Audience campaign dispatch and Segmentation and 1 more component, lasting 3h 33m. The incident has been resolved; the full update timeline is below.

Started
Apr 30, 2024, 04:09 PM UTC
Resolved
Apr 30, 2024, 07:42 PM UTC
Duration
3h 33m
Detected by Pingoru
Apr 30, 2024, 04:09 PM UTC

Affected components

Audience campaign dispatchSegmentationRealtime campaign dispatchStories Dispatch

Update timeline

  1. identified Apr 30, 2024, 04:09 PM UTC

    We are currently experiencing degraded platform performance connected to segmentation. In order to implement measures to solve it we have paused message dispatching. Our engineers are currently working on this. We will publish an update as soon as campaign execution resumes. Please accept our apologies for the inconvenience this causes and please do reach out if you have any further queries.

  2. identified Apr 30, 2024, 05:10 PM UTC

    The issue has been identified and a fix is being implemented

  3. monitoring Apr 30, 2024, 06:08 PM UTC

    The issue has been identified and a fix has been implemented. We are rapidly consuming data queues & will keep monitoring in the coming hours. Our apologies for the inconvenience this might have caused.

  4. resolved Apr 30, 2024, 07:42 PM UTC

    As of 9 pm, the event lag has been fully processed and all events were fully caught up. After thoroughly monitoring our systems we are marking this incident as resolved. We apologize if this delay caused any inconvenience. Feel free to get in touch with us if you have any questions. Your CrossEngage team.