Company Logo

Is there an CrossEngage outage?

CrossEngage status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for CrossEngage and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

CrossEngage outages and incidents

Outage and incident data over the last 30 days for CrossEngage.

There have been 0 outages or incidents for CrossEngage in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for CrossEngage

Outlogger tracks the status of these components for Xero:

Segmentation Active
User Interface Active
Web tracking Active
API v1.0 Active
API v2.0 Active
Audience campaign dispatch Active
Realtime campaign dispatch Active
Stories Dispatch Active
Google Apps Analytics Active
mailgun API Active
mailgun Events & Logs Active
Mandrill Mandrill Global Active
SendGrid API Active
SendGrid API v2 Active
SendGrid API v3 Active
SendGrid Email Activity Active
SendGrid Event Webhook Active
SendGrid Marketing Campaigns Active
Twilio REST API Active
Twilio SMS Active
Customer Prediction Platform Active
Component Status
Segmentation Active
User Interface Active
Web tracking Active
Active
API v1.0 Active
API v2.0 Active
Active
Audience campaign dispatch Active
Realtime campaign dispatch Active
Stories Dispatch Active
Active
Google Apps Analytics Active
mailgun API Active
mailgun Events & Logs Active
Mandrill Mandrill Global Active
SendGrid API Active
SendGrid API v2 Active
SendGrid API v3 Active
SendGrid Email Activity Active
SendGrid Event Webhook Active
SendGrid Marketing Campaigns Active
Twilio REST API Active
Twilio SMS Active
Active
Customer Prediction Platform Active

Latest CrossEngage outages and incidents.

View the latest incidents for CrossEngage and check for official updates:

Updates:

  • Time: Sept. 1, 2020, 5:44 p.m.
    Status: Resolved
    Update: A solution has been implemented and we are now continuing realtime and audience campaign dispatching. All events which have been queued for realtime campaigns will be processed accordingly and will trigger dispatch as expected. All audience campaigns which have been paused will start/continue dispatching again. Our apologies for the inconvenience this might have caused. Your CrossEngage team
  • Time: Sept. 1, 2020, 3:24 p.m.
    Status: Investigating
    Update: We are currently experiencing degraded platform performance. As a safety measure, we have disabled campaigns dispatching. User updates and events are being processed as expected. Our engineers are currently working on rectifying 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.

Updates:

  • Time: Sept. 1, 2020, 5:44 p.m.
    Status: Resolved
    Update: A solution has been implemented and we are now continuing realtime and audience campaign dispatching. All events which have been queued for realtime campaigns will be processed accordingly and will trigger dispatch as expected. All audience campaigns which have been paused will start/continue dispatching again. Our apologies for the inconvenience this might have caused. Your CrossEngage team
  • Time: Sept. 1, 2020, 3:24 p.m.
    Status: Investigating
    Update: We are currently experiencing degraded platform performance. As a safety measure, we have disabled campaigns dispatching. User updates and events are being processed as expected. Our engineers are currently working on rectifying 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.

Updates:

  • Time: Aug. 23, 2020, 9:50 p.m.
    Status: Resolved
    Update: After thoroughly monitoring our systems and not having identified any further data processing delays we are marking this incident as resolved. Feel free to reach out if you have any further questions.
  • Time: Aug. 23, 2020, 9:50 p.m.
    Status: Resolved
    Update: After thoroughly monitoring our systems and not having identified any further data processing delays we are marking this incident as resolved. Feel free to reach out if you have any further questions.
  • Time: Aug. 23, 2020, 8:46 p.m.
    Status: Monitoring
    Update: Our platform has recovered and it is now fully operational. As of 22:40 CET the queue has been processed and all incoming data is being consumed without any delay. Our engineering team will keep monitoring systems closely.
  • Time: Aug. 23, 2020, 8:46 p.m.
    Status: Monitoring
    Update: Our platform has recovered and it is now fully operational. As of 22:40 CET the queue has been processed and all incoming data is being consumed without any delay. Our engineering team will keep monitoring systems closely.
  • Time: Aug. 23, 2020, 7:17 p.m.
    Status: Identified
    Update: We have identified the cause of the delay in data processing.
  • Time: Aug. 23, 2020, 7:17 p.m.
    Status: Identified
    Update: We have identified the cause of the delay in data processing.
  • Time: Aug. 23, 2020, 3:41 p.m.
    Status: Investigating
    Update: We have identified a delay in the processing of updates sent through our API. This affects both user attribute updates and event data. The data is received and queued by our system but will only be processed and visible in your segments with delay. Our Engineering Team is currently investigating this and we will post updates as they become available. Please accept our apologies for the inconvenience this causes and do let our Support Team know if you have any questions on this. Thank you very much for your understanding.
  • Time: Aug. 23, 2020, 3:41 p.m.
    Status: Investigating
    Update: We have identified a delay in the processing of updates sent through our API. This affects both user attribute updates and event data. The data is received and queued by our system but will only be processed and visible in your segments with delay. Our Engineering Team is currently investigating this and we will post updates as they become available. Please accept our apologies for the inconvenience this causes and do let our Support Team know if you have any questions on this. Thank you very much for your understanding.

Updates:

  • Time: Aug. 13, 2020, 6:44 a.m.
    Status: Resolved
    Update: This incident has been resolved and you should now be able to login. Sincere apologies for the inconvenience and thank you for your understanding.
  • Time: Aug. 13, 2020, 6:44 a.m.
    Status: Resolved
    Update: This incident has been resolved and you should now be able to login. Sincere apologies for the inconvenience and thank you for your understanding.
  • Time: Aug. 13, 2020, 6:37 a.m.
    Status: Investigating
    Update: We are currently investigating an issue with login which have been reported this morning. Our engineers are currently working on rectifying this. We will publish an update as soon as login is back to normal. Please accept our apologies for the inconvenience this causes and do reach out if you have any further queries.
  • Time: Aug. 13, 2020, 6:37 a.m.
    Status: Investigating
    Update: We are currently investigating an issue with login which have been reported this morning. Our engineers are currently working on rectifying this. We will publish an update as soon as login is back to normal. Please accept our apologies for the inconvenience this causes and do reach out if you have any further queries.

Updates:

  • Time: July 29, 2020, 2:15 p.m.
    Status: Resolved
    Update: Our Engineering Team has closely monitored data processing and concluded that all systems functioned without any delay. Please feel free to get in touch if you have any questions. Thank you for your understanding
  • Time: July 29, 2020, 1:25 p.m.
    Status: Monitoring
    Update: We are seeing improvements in our data processing. We will monitor its progress and we will post an update as soon as the platform is processing all data without any delays.
  • Time: July 29, 2020, 11:29 a.m.
    Status: Investigating
    Update: We have identified a delay in the processing of updates sent through our API. This affects both user attribute updates and event data. The data is received and queued by our system but will only be processed and visible in your segments after a waiting time of approximately 50 minutes. Existing campaigns are not affected and are dispatched as usual. Our Engineering Team is currently investigating this and we will post updates as they become available. Please accept our apologies for the inconvenience this causes and do let our Support Team know if you have any questions on this. Thank you very much for your understanding.

Check the status of similar companies and alternatives to CrossEngage

Akamai
Akamai

Systems Active

Nutanix
Nutanix

Systems Active

MongoDB
MongoDB

Systems Active

LogicMonitor
LogicMonitor

Systems Active

Acquia
Acquia

Systems Active

Granicus System
Granicus System

Systems Active

CareCloud
CareCloud

Systems Active

Redis
Redis

Systems Active

integrator.io
integrator.io

Systems Active

NinjaOne Trust

Systems Active

Pantheon Operations
Pantheon Operations

Systems Active

Securiti US
Securiti US

Systems Active

Frequently Asked Questions - CrossEngage

Is there a CrossEngage outage?
The current status of CrossEngage is: Systems Active
Where can I find the official status page of CrossEngage?
The official status page for CrossEngage is here
How can I get notified if CrossEngage is down or experiencing an outage?
To get notified of any status changes to CrossEngage, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of CrossEngage every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here