CrossEngage Outage History

CrossEngage is up right now

CrossEngage had 19 outages in the last 2 years totaling 33h 10m of downtime — averaging 0.8 incidents per month.

There were 19 CrossEngage outages since May 25, 2024 totaling 33h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.crossengage.io

Minor May 9, 2026

Degraded platform performance

Detected by Pingoru
May 09, 2026, 07:02 AM UTC
Resolved
May 09, 2026, 08:17 AM UTC
Duration
1h 14m
Affected: Audience campaign dispatchUser InterfaceAPI v1.0SegmentationRealtime campaign dispatchAPI v2.0Web trackingStories DispatchExport API
Timeline · 3 updates
  1. identified May 09, 2026, 07:02 AM UTC

    Dear customer, We are currently experiencing degraded platform performance due to a data center network issue, impacting data ingestion. Our Engineering team is actively investigating and working close with data center to resolve the problem. We will continue to share updates as more information becomes available. We apologize for the inconvenience and appreciate your patience. Please reach out if you have any questions. Your ActivatePro Team

  2. monitoring May 09, 2026, 07:53 AM UTC

    Our data center is again available and we are monitoring the situation.

  3. resolved May 09, 2026, 08:17 AM UTC

    Dear customer, this incident was resolved. All our systems are working properly again. We are sorry for the inconvenience. Your ActivatePro Team

Read the full incident report →

Minor March 5, 2026

Partial Login and API interruption

Detected by Pingoru
Mar 05, 2026, 07:51 AM UTC
Resolved
Mar 05, 2026, 07:51 AM UTC
Duration
Timeline · 1 update
  1. monitoring Mar 05, 2026, 07:51 AM UTC

    Mar 5, 08:51 CET Resolved - This incident has been resolved. Mar 4, 17:07 CET Monitoring - A fix has been implemented and we are monitoring the results. Mar 4, 14:57 CET Identified - Dear customers, Some users are currently unable to log in to both the CDP and the prediction platform. APIs may be affected as well. Our engineers are investigating the cause. We will update as soon as we have more information. We sincerely apologize for any inconvenience. Your ActivatePro team

Read the full incident report →

Minor January 8, 2026

Degraded performance of Webhooks via Stories

Detected by Pingoru
Jan 08, 2026, 01:05 PM UTC
Resolved
Jan 08, 2026, 01:05 PM UTC
Duration
Timeline · 1 update
  1. monitoring Jan 08, 2026, 01:05 PM UTC

    Jan 8, 14:05 CET Resolved - This incident has been resolved. Jan 8, 09:57 CET Monitoring - A fix was implemented yesterday and all systems should be back to normal. We will keep actively monitoring the system over the upcoming hours. Your ActivatePro Team. Jan 7, 12:55 CET Identified - Dear customers, we have detected dispatching issues in Stories connected to Webhooks - the dispatch of Webhooks via Stories is currently unreliable. This results in some cases in delayed or possible missed dispatches. Our developers are already working on a fix and we will update you as soon a fix is implemented. We apologize for the inconvenience. Your ActivatePro Team

Read the full incident report →

Minor November 18, 2025

Instable availability of our services

Detected by Pingoru
Nov 18, 2025, 06:56 PM UTC
Resolved
Nov 18, 2025, 06:56 PM UTC
Duration
Timeline · 1 update
  1. monitoring Nov 18, 2025, 06:56 PM UTC

    Nov 18, 19:56 CET Resolved - This incident has been resolved. Nov 18, 15:48 CET Monitoring - Cloudflare implemented a fix and believes the incident to be resolved. All services are available again, but we will keep monitoring for the next few hours. Your ActivatePro Team Nov 18, 14:21 CET Identified - Dear Customers, we are currently experiencing network issues connected to the active global Cloudflare outage. This causes instable availability of our services and possible delayed processing of data. Most affected are the UI and the Tracking API, but other components could be affected as well. We are sorry for the inconvenience. Your ActivatePro Team

Read the full incident report →

Minor August 20, 2025

Extention of Scheduled Maintenance

Detected by Pingoru
Aug 20, 2025, 05:13 AM UTC
Resolved
Aug 20, 2025, 05:13 AM UTC
Duration
Timeline · 1 update
  1. monitoring Aug 20, 2025, 05:13 AM UTC

    Aug 20, 07:13 CEST Completed - The scheduled maintenance has been completed. All services are resumed and operational. Warm regards, Your ActivatePro Team Aug 20, 06:23 CEST Update - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 20, 06:22 CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug 20, 06:21 CEST Scheduled - We just got informed that the previous just completed scheduled maintenace (August 20th, between 12AM (midnight) and 6AM CEST) in our data center had to get extended as they are still working on the essential maintenance. We understand that any downtime can be inconvenient, and we sincerely appreciate your patience and understanding as we work to enhance your experience with our platform. Thank you for your continued support. Warm regards, Your ActivatePro Team

Read the full incident report →

Notice January 28, 2025

Degraded Indexing Performace

Detected by Pingoru
Jan 28, 2025, 04:20 PM UTC
Resolved
Jan 28, 2025, 08:55 PM UTC
Duration
4h 35m
Timeline · 3 updates
  1. investigating Jan 28, 2025, 04:20 PM UTC

    We have detected a delay in processing/indexing of events. This affects event data, user updates are processed normally. The data is queuing and it will be visible in your segments with delay. Campaign dispatching is not directly affected, but segmentation might be affected. Our Engineering Team is already working on it. Your CrossEngage Team.

  2. monitoring Jan 28, 2025, 05:48 PM UTC

    Everything is back to normal. Our engineers will keep monitoring the situation in the upcoming hours, but no more disruption is expected. Your CrossEngage Team.

  3. resolved Jan 28, 2025, 08:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 22, 2024

Degraded Platform Performance Segmentation

Detected by Pingoru
Nov 22, 2024, 10:49 AM UTC
Resolved
Nov 22, 2024, 03:09 PM UTC
Duration
4h 20m
Affected: Segmentation
Timeline · 3 updates
  1. identified Nov 22, 2024, 10:49 AM UTC

    We noticed that our segmentation performance is degraded, event updates are queued. Our Engineering Team is on it and we will post an update as soon as one is available. Your CrossEngage Team.

  2. monitoring Nov 22, 2024, 12:34 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 22, 2024, 03:09 PM UTC

    This incident has been resolved. If you have any questions, feel free to write to us. Your CrossEngage Team.

Read the full incident report →

Minor November 20, 2024

Degraded Platform Performance- Segmentation

Detected by Pingoru
Nov 20, 2024, 02:12 PM UTC
Resolved
Nov 20, 2024, 06:44 PM UTC
Duration
4h 32m
Affected: Segmentation
Timeline · 3 updates
  1. identified Nov 20, 2024, 02:12 PM UTC

    We noticed that our segmentation performance is degraded, event updates are queued. Our Engineering Team is on it and we will post an update as soon as one is available. Your CrossEngage Team.

  2. monitoring Nov 20, 2024, 04:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 20, 2024, 06:44 PM UTC

    This incident has been resolved. If you have any questions, feel free to write to us. Your CrossEngage Team.

Read the full incident report →

Minor October 29, 2024

Data Processing Delay

Detected by Pingoru
Oct 29, 2024, 01:42 PM UTC
Resolved
Oct 29, 2024, 06:36 PM UTC
Duration
4h 53m
Affected: API v1.0SegmentationAPI v2.0Web tracking
Timeline · 3 updates
  1. identified Oct 29, 2024, 01:42 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 events 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. monitoring Oct 29, 2024, 02:31 PM UTC

    The event lag has now been fully processed as of 15:25 (CET) and all events are fully caught up. We will keep the state of this incident in monitoring for a few more hours. If you have any questions feel free to reach out to us. Your CrossEngage Team.

  3. resolved Oct 29, 2024, 06:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 9, 2024

Degraded performance on data ingestion

Detected by Pingoru
Oct 09, 2024, 03:21 PM UTC
Resolved
Oct 09, 2024, 05:54 PM UTC
Duration
2h 32m
Affected: Segmentation
Timeline · 3 updates
  1. identified Oct 09, 2024, 03:21 PM UTC

    We have detected a delay in processing/indexing of some user updates, events are processed normally. Our Engineering Team is on it and we will post an update as soon as one is available. Your CrossEngage Team.

  2. monitoring Oct 09, 2024, 04:27 PM UTC

    A fix has been implemented. We are rapidly consuming data queues & will keep monitoring in the coming hours.

  3. resolved Oct 09, 2024, 05:54 PM UTC

    All queued data has been fully processed and all systems are processing data normally again. After thoroughly monitoring our systems we are marking this incident as resolved. We apologize if this delay caused any inconvenience. Your CrossEngage team.

Read the full incident report →

Minor August 15, 2024

Degraded indexing performance

Detected by Pingoru
Aug 15, 2024, 05:30 PM UTC
Resolved
Aug 15, 2024, 08:36 PM UTC
Duration
3h 6m
Affected: API v1.0SegmentationAPI v2.0Web tracking
Timeline · 3 updates
  1. identified Aug 15, 2024, 05:30 PM UTC

    We have detected a delay in processing/indexing of events. This affects event data, user updates are processed normally. Our system receives and queues the data and it will be visible in your segments with delay. Campaign dispatching is not directly affected, but segmentation might be affected. Our Engineering Team is on it and we will post an update as soon as one is available. Your CrossEngage Team.

  2. monitoring Aug 15, 2024, 06:44 PM UTC

    All systems are back to normal. Our engineers will keep monitoring the situation in the upcoming hours, but no more disruption is expected. Your CrossEngage Team.

  3. resolved Aug 15, 2024, 08:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 5, 2024

Delayed Processing of User Updates

Detected by Pingoru
Jul 05, 2024, 08:24 AM UTC
Resolved
Jul 05, 2024, 12:51 PM UTC
Duration
4h 27m
Affected: Segmentation
Timeline · 2 updates
  1. monitoring Jul 05, 2024, 08:24 AM UTC

    We are currently experiencing a high load of user updates which has created a lag and user updates are processed with a delay. Event processing is not affected by this. If you have any questions, feel free to reach out to us. Your CrossEngage Team.

  2. resolved Jul 05, 2024, 12:51 PM UTC

    The user update queue has been fully processed as of 13:00. We are changing the status to resolved. If you have any questions, feel free to write to us. Your CrossEngage Team.

Read the full incident report →

Major June 28, 2024

Log in interrupted

Detected by Pingoru
Jun 28, 2024, 11:06 AM UTC
Resolved
Jun 28, 2024, 02:35 PM UTC
Duration
3h 29m
Affected: User Interface
Timeline · 4 updates
  1. investigating Jun 28, 2024, 11:06 AM UTC

    It is currently not possible to login into our platform. Our engineers are currently working on rectifying this. We will publish an update as soon as logging in is possible again. All other services are running normally.

  2. identified Jun 28, 2024, 12:37 PM UTC

    A fix has been implemented and we see improvement. Our engineers are currently still working on identifying and implementing additional measures. Sincere apologies for the inconvenience. Your CrossEngage Team

  3. monitoring Jun 28, 2024, 01:07 PM UTC

    A fix has been implemented and the login is working as expected. Our team will continue to closely monitor the platform. Sincere apologies for the inconvenience and thank you for your understanding. Your CrossEngage Team

  4. resolved Jun 28, 2024, 02:35 PM UTC

    We don't see any irregularities anymore and are now closing this topic. Your CrossEngage Team

Read the full incident report →