CrossEngage incident

Degraded Indexing Performance

Minor Resolved View vendor source →

CrossEngage experienced a minor incident on April 17, 2025 affecting Audience campaign dispatch and API v1.0 and 1 more component, lasting 4h 59m. The incident has been resolved; the full update timeline is below.

Started
Apr 17, 2025, 05:35 PM UTC
Resolved
Apr 17, 2025, 10:35 PM UTC
Duration
4h 59m
Detected by Pingoru
Apr 17, 2025, 05:35 PM UTC

Affected components

Audience campaign dispatchAPI v1.0SegmentationRealtime campaign dispatchAPI v2.0Web trackingStories Dispatch

Update timeline

  1. investigating Apr 17, 2025, 05:35 PM UTC

    We have detected a delay in the processing of updates sent to our system. Our system receives and queues the data and it will be visible in your segments with delay. Campaign dispatching is not affected, but segmenting might be as most recent updates are not instantly visible. Our Engineering Team is on it and we will post an update as soon as one is available. Your CrossEngage Team.

  2. identified Apr 17, 2025, 07:08 PM UTC

    A fix has been implemented and we are consuming data queues. We will keep monitoring for the next hours. We also identified a connected issue with the connection to the Product feed, which in some cases can effect the dispatch of messages as well. Our engineers are working on a fix right now. Your ActivatePro Team.

  3. monitoring Apr 17, 2025, 07:41 PM UTC

    A fix has been implemented and the product feed is available again. We will keep monitoring for the next hours. We are sorry for the inconvenience. Your ActivatePro Team.

  4. resolved Apr 17, 2025, 10:35 PM UTC

    This incident has been resolved.