MoEngage Outage History

Started Oct 20, 2026, 08:43 AM UTC· resolved Oct 20, 2026, 01:03 PM UTC

1. investigating Oct 20, 2026, 08:43 AM UTC

   We’re currently experiencing an issue affecting the availability of the MoEngage website, including our documentation and knowledge base at https://moengage.com/docs. Our team is actively investigating and working to restore access as quickly as possible. The MoEngage dashboard, APIs, SDKs, and campaign delivery are not affected.

2. investigating Oct 20, 2026, 11:12 AM UTC

   We are continuing to investigate the issue.

3. resolved Oct 20, 2026, 01:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 24, 2026, 11:39 AM UTC· resolved Sep 24, 2026, 12:23 PM UTC

1. investigating Sep 24, 2026, 11:39 AM UTC

   We are currently investigating an issue affecting the campaign listing page on the dashboard. Some users may see intermittent errors while loading or viewing their campaigns listing. Our engineering team is actively working on this, and we will share the next update within 30 minutes or sooner as more information becomes available.

2. monitoring Sep 24, 2026, 11:48 AM UTC

   We are actively monitoring after a fix.

3. resolved Sep 24, 2026, 12:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 17, 2026, 02:25 PM UTC· resolved Aug 18, 2026, 06:30 AM UTC

1. resolved Aug 18, 2026, 10:31 AM UTC

   Summary Between 2026-08-17 at 19:55 IST and 2026-08-18 at 12:21 IST, a subset of requests made to the Inform API may not have been delivered successfully. Affected requests received an HTTP 200 OK response, indicating success, but the corresponding messages were never sent. The issue has been fully resolved as of 2026-08-18 at 12:21 IST. Impact - Customers using the Inform API routed through DC-03 during the affected window may have been impacted - Affected requests appeared successful on the client side but were not processed - As a result, messages associated with those requests were not delivered - We are unable to automatically retry or replay the affected requests What We Did We identified the issue during a routine internal routing update and immediately rolled back the change. Full service was restored at 2026-08-18 at 12:21 IST. What You Should Do If you believe your integration was affected during this window, we recommend: - Reviewing your logs for requests made between 2026-08-17 19:55 IST and 2026-08-18 12:21 IST - Identifying any messages that were not delivered as expected - Re-sending those requests manually if delivery is still required We sincerely apologize for the inconvenience this may have caused. If you have any questions or need assistance identifying affected requests, please reach out to our support team.

Read the full incident report →

Started Jul 27, 2026, 10:07 AM UTC· resolved Jul 27, 2026, 02:47 PM UTC

1. investigating Jul 27, 2026, 10:07 AM UTC

   We are currently experiencing degraded performance across multiple services. Our engineering team is actively investigating the issue and working to restore full service as quickly as possible. What We Know So Far Multiple services are experiencing degraded performance Outbound channels are particularly impacted and some users may experience delays or failures with outbound message delivery Our team has identified a potential issue with our underlying cloud infrastructure and is actively investigating What We Are Doing Our engineering team is actively investigating the root cause and is working to restore full service. We will share more details as they become available. We will provide our next update within 30 minutes. We sincerely apologize for the disruption this may be causing to your operations. Thank you for your patience and understanding while we work to resolve this.

2. investigating Jul 27, 2026, 10:12 AM UTC

   We have identified that our servers are experiencing delays in scaling up within our cloud infrastructure. This is causing campaign sending to be significantly slower than normal as a result. Our engineering team is actively working on a resolution and we will provide a further update shortly.

3. investigating Jul 27, 2026, 10:13 AM UTC

   Event Triggered Campaigns and Flows are also experiencing degraded performance. Our team continues to work on a resolution and we will provide a further update shortly.

4. investigating Jul 27, 2026, 10:32 AM UTC

   Our engineering team has implemented a temporary workaround which has helped improve performance. Campaign sending has resumed, however you may still experience slower than usual delivery speeds while we continue to work on a full resolution. We will provide a further update shortly.

5. identified Jul 27, 2026, 11:07 AM UTC

   Our cloud infrastructure provider is currently experiencing issues which are impacting our services. We are in active communication with them and are working together to achieve a full recovery. We are seeing gradual improvement and services are beginning to recover, however this may take some time. We appreciate your continued patience while we work towards full resolution. We will provide a further update shortly.

6. monitoring Jul 27, 2026, 11:38 AM UTC

   We are pleased to confirm that our engineering team has identified the root cause and successfully applied a fix. Our infrastructure has recovered rapidly and we are seeing strong improvement across all affected services. Services have returned to normal and we are in the process of clearing the remaining backlog. We will post a final update once the backlog has been fully cleared. Thank you for your patience and understanding throughout this incident.

7. resolved Jul 27, 2026, 02:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 25, 2026, 09:11 AM UTC· resolved Jul 25, 2026, 12:00 PM UTC

1. investigating Jul 25, 2026, 09:11 AM UTC

   We are currently investigating issue related to following services in DC01: - Inform - Event Triggered Campaigns and Flow

2. investigating Jul 25, 2026, 09:18 AM UTC

   We are continuing to investigate this issue.

3. investigating Jul 25, 2026, 09:53 AM UTC

   We are continuing to investigate this issue.

4. investigating Jul 25, 2026, 09:54 AM UTC

   We continue to work on mitigation.

5. monitoring Jul 25, 2026, 11:36 AM UTC

   We are currently monitoring services

6. resolved Jul 25, 2026, 12:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 05:00 AM UTC· resolved Jun 01, 2026, 08:35 AM UTC

1. resolved Jun 01, 2026, 10:02 AM UTC

   Between 05:00 UTC and 08:35 UTC, the Branded Email Link Click Domain service in the DC-02 region experienced an extended period of performance degradation, followed by a brief period of unavailability. Impact: 05:00 UTC – 08:00 UTC: The service operated in a degraded state. Some users may have experienced delayed responses or intermittent timeouts when clicking branded email links for a limited number of affected brands. 08:00 UTC – 08:35 UTC: The service was unavailable while our engineering team performed recovery actions. Normal service was fully restored at 08:35 UTC. Root Cause: The degradation was caused by an unexpected and significant spike in request volume. This sudden increase in traffic placed excessive load on the backend database, resulting in slower query processing and degraded service performance. Resolution: Our monitoring systems detected the degradation and alerted the engineering team. To restore stability and support the increased traffic volume, the team scaled the underlying database infrastructure and completed recovery procedures. After the infrastructure changes were completed, service availability and performance returned to normal at 08:35 UTC. Current Status The issue has been resolved, and the Branded Email Link Click Domain service is operating normally in the DC-02 region. We apologize for the disruption and any inconvenience this may have caused.

Read the full incident report →

Started May 31, 2026, 10:30 PM UTC· resolved Jun 01, 2026, 04:00 AM UTC

1. resolved Jun 04, 2026, 10:17 AM UTC

   On June 1, 2026, we experienced a major incident that affected the processing of email delivery status events in two of our data centers; Dashboard 02 and 04. During this incident, some delivery-related events — including delivered, bounce, and spam status updates — were not processed correctly. As a result, customers may have seen incomplete or under-reported delivery statistics in dashboards and reports for campaigns sent during the affected period. We want to emphasize that actual email sending and delivery to recipients were not impacted. The issue was limited to the reporting and processing of delivery status events. The incident was triggered by a recent internal system update that changed how delivery events are grouped and processed. In some environments, this caused certain event batches to fail processing. Our monitoring did not alert us as quickly as expected, which delayed detection and response. We sincerely apologize for the impact this had on your visibility into campaign performance and for the delay in identifying the issue. Our teams have taken corrective action to resolve the issue and are reviewing the affected data. We are also strengthening our monitoring, validation, and release safeguards to help prevent similar incidents in the future. We understand how important accurate and timely delivery reporting is to your business, and we regret the disruption this caused. Thank you for your patience and understanding while we worked through this incident.

Read the full incident report →

Started May 14, 2026, 09:55 AM UTC· resolved May 14, 2026, 03:01 PM UTC

1. investigating May 14, 2026, 09:55 AM UTC

   We are experiencing delay in our user and event ingestion pipeline. The issue started around 10am IST on 14-May. This impacts all the ingestion to be delayed resulting in stale data availability in downstream systems. The team has identified the issue and released a patch for the fix. The current delay is ~3hours.

2. monitoring May 14, 2026, 09:57 AM UTC

   The fix has been implemented and the lag is coming down. Current lag is ~3hours. The team is monitoring the systems

3. monitoring May 14, 2026, 11:35 AM UTC

   We are continuously monitoring the situation. The lag is slowly going down as we have provisioned more infrastructure. Current lag is ~2.5 hours.

4. resolved May 14, 2026, 03:01 PM UTC

   The lag is cleared and latency is within our SLA threshold. The team will take corrective actions as part of the incident post mortem.

Read the full incident report →

Started May 13, 2026, 10:02 PM UTC· resolved May 14, 2026, 03:39 AM UTC

1. monitoring May 13, 2026, 10:02 PM UTC

   We observed delay in data processing for DC04, subsequently Issue was identified. We are actively monitoring data processing lag for DC 04.

2. resolved May 14, 2026, 03:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 24, 2026, 04:35 AM UTC· resolved Apr 24, 2026, 05:27 AM UTC

1. monitoring Apr 24, 2026, 04:35 AM UTC

   There was a degradation in our querying service (Segmentation). The issue started at 3:00 UTC and is resolved now. We are now rerunning the failed campaigns. All delayed campaigns should be sent out in the next 45-60 minutes.

2. resolved Apr 24, 2026, 05:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 21, 2026, 01:45 AM UTC· resolved Apr 21, 2026, 01:45 AM UTC

1. monitoring Apr 20, 2026, 10:35 AM UTC

   Apr 20, 10:34 UTC Monitoring - We experienced a lag in our data ingestion pipeline between 8:00 AM UTC and 9:00 AM UTC due to an underlying system issue. A hotfix was deployed at approximately 8:45 AM UTC to address the problem. The system is now operating normally and we are actively monitoring it. During the incident window, some processing lag accumulated, which is currently being cleared. We expect the backlog to be fully processed within the next two hours. We apologize for the inconvenience caused and appreciate your patience while we worked to resolve the issue.

Read the full incident report →

Started Apr 19, 2026, 10:42 PM UTC· resolved Apr 19, 2026, 11:11 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Apr 09, 2026, 08:39 AM UTC· resolved Apr 09, 2026, 08:39 AM UTC

1. resolved Apr 09, 2026, 08:39 AM UTC

   Apr 9, 08:39 UTC Resolved - There was a degradation identified on DC03 Data Ingestion pipeline since 9th Apr, 10:30 AM IST. This was due to an infra/instance type change which was deployed. This change seemed to be unstable and hence has been reverted now. It resulted in degraded data processing throughput resulting in lag. Duration of the incident: 10:30am IST - 01:45pm IST (~3.15 hours) Impact: The delay in data processing has impact on availability of user updates and events in segmentation. it also had an impact on Event triggered campaigns and flows due to the delay. Resolution: The lag has been recovered as of 01:45pm IST. There is no data loss. Team is currently monitoring the systems and doing a deeper post-mortem to avoid such occurrence in future.

Read the full incident report →

Started Mar 31, 2026, 11:41 AM UTC· resolved Mar 31, 2026, 11:41 AM UTC

1. resolved Mar 31, 2026, 11:41 AM UTC

   Mar 31, 11:41 UTC Resolved - This incident has been resolved. The lag was observed from 06:45 UTC (12:15pm IST) to 11:30 UTC (05:00pm IST). Mar 31, 11:11 UTC Monitoring - We are currently experiencing degraded performance in our Trigger-Based Flows system. This is causing delays of up to 45 minutes in user entry and movement within Trigger-Based Flows. Please note that Event-Triggered Campaigns remain unaffected. Our team has fixed the issue and is actively monitoring the system. We apologize for the inconvenience and appreciate your patience as we work to resolve this.

Read the full incident report →

Started Mar 24, 2026, 03:54 PM UTC· resolved Mar 24, 2026, 03:54 PM UTC

1. resolved Mar 24, 2026, 03:54 PM UTC

   Mar 24, 15:54 UTC Resolved - The issue is resolved as of now and ingestion pipeline latency seems stable. However, the technical team is root causing the issue to deploy a permanent fix. This data ingestion delay had an impact on Smart trigger campaigns and Flows, as it consumes the data from the ingestion pipeline and apply trigger/flows conditions. Delay of around 45 min lasted between 24-March 13:00 UTC to 15:40 UTC. There were delay observed later as well on 24-March 20:30 UTC to 21:30 UTC. Mar 24, 14:47 UTC Identified - There is a delay of close to 45 min in DC-03 starting 13:00 UTC of users and events in our ingestion pipeline. We expect the issue to be resolved in another 45 min.

Read the full incident report →

Started Mar 13, 2026, 05:16 AM UTC· resolved Mar 13, 2026, 05:16 AM UTC

1. resolved Mar 13, 2026, 05:16 AM UTC

   Mar 13, 05:16 UTC Resolved - This incident has been resolved. Mar 13, 03:11 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 13, 02:32 UTC Identified - The issue has been identified and a fix is being implemented. Mar 13, 02:13 UTC Update - We are continuing to investigate this issue. Mar 13, 02:12 UTC Investigating - Team is currently working on investigating following impacted services in DC03 - Smart Trigger & Flow Campaigns We apologize for inconvenience this may have caused and appreciate your patience. For any queries or immediate concerns, please do not hesitate to contact our support team.

Read the full incident report →

Started Mar 12, 2026, 07:18 PM UTC· resolved Mar 12, 2026, 07:18 PM UTC

1. resolved Mar 12, 2026, 07:18 PM UTC

   Mar 12, 19:18 UTC Resolved - This incident has been resolved. Mar 12, 17:05 UTC Identified - We are currently experiencing a delay in the data ingestion pipeline for following services: 1. Event Triggered Campaigns and Flows 2. Inbound Campaigns (In-App, OSM, WebP) 3. Recent Activity on User Profile We have identified the issue and mitigation has been deployed and lag is being monitored closely by teams.

Read the full incident report →

Started Mar 06, 2026, 11:06 AM UTC· resolved Mar 06, 2026, 11:06 AM UTC

1. resolved Mar 06, 2026, 11:06 AM UTC

   Mar 6, 11:06 UTC Resolved - The incident has been resolved. The issue lasted for 30 min from 10:35 to 11:05 UTC. Mar 6, 11:05 UTC Update - We are continuing to monitor for any further issues. Mar 6, 10:56 UTC Monitoring - All Campaigns Page is not loading since 10:35 UTC on DC-02. A fix has been implemented and issue should be resolved in the next 10 minutes.

Read the full incident report →

Started Mar 05, 2026, 05:15 PM UTC· resolved Mar 05, 2026, 05:15 PM UTC

1. resolved Mar 05, 2026, 05:15 PM UTC

   Mar 5, 17:15 UTC Resolved - This incident has been resolved. Mar 5, 16:29 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 5, 15:31 UTC Update - We are continuing to work on a fix for this issue. Mar 5, 15:31 UTC Identified - The issue has been identified and a fix is being implemented. Mar 5, 15:28 UTC Investigating - We are currently experiencing delay with the Stats update in Dashboard 03. Please note that campaign sending is not impacted; however, the latest statistics may be delayed on the dashboard at this time. Our team is treating this as a top priority and is working to resolve the issue as quickly as possible. Thank you for your patience.

Read the full incident report →

Started Feb 25, 2026, 12:18 PM UTC· resolved Feb 25, 2026, 12:18 PM UTC

1. resolved Feb 25, 2026, 12:18 PM UTC

   Feb 25, 12:18 UTC Resolved - This incident has been resolved. Feb 25, 12:16 UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb 25, 12:05 UTC Investigating - We are currently investigating the issue.

Read the full incident report →

Started Feb 19, 2026, 08:30 PM UTC· resolved Feb 19, 2026, 08:30 PM UTC

1. resolved Feb 19, 2026, 08:30 PM UTC

   Feb 19, 20:30 UTC Completed - The scheduled maintenance has been completed. Feb 19, 18:22 UTC Update - We have paused our data processing systems and initiated cluster resizing. Feb 19, 17:30 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 17, 08:52 UTC Scheduled - Hello, To ensure the long-term stability and efficiency of our data pipelines, we will be resizing our Kafka and Data Warehouse clusters during a scheduled maintenance window on Feb 19-20. Schedule: Window: Feb 19, 17:30 PM UTC – Feb 19, 20:30 PM UTC Duration: 3 hours Service Impact: To facilitate the rebalancing of our data brokers, users may experience transient latency in data ingestion. This means that while user and events are being successfully received, they may take longer to reflect in downstream reports, segmentation, campaign stats and analytics. Technical Note: Once the cluster rebalancing is complete, the system will automatically clear any accumulated backlogs. We do not anticipate any data loss or service downtime. There will not be any impact on campaign sending schedules.

Read the full incident report →

Started Feb 11, 2026, 05:50 PM UTC· resolved Feb 11, 2026, 05:50 PM UTC

1. resolved Feb 11, 2026, 05:50 PM UTC

   Feb 11, 17:50 UTC Resolved - This incident has been resolved. Feb 11, 16:16 UTC Update - We are continuing to monitor for any further issues. Feb 11, 16:12 UTC Monitoring - We are experiencing a delay of around 90 minutes in processing data imports & exports. A fix has been implemented and currently the system is recovering.

Read the full incident report →

Started Feb 11, 2026, 03:31 AM UTC· resolved Feb 11, 2026, 03:31 AM UTC

1. resolved Feb 11, 2026, 03:31 AM UTC

   Feb 11, 03:31 UTC Resolved - This incident has been resolved. Feb 10, 22:56 UTC Update - We are continuing to monitor for any further issues. Feb 10, 22:52 UTC Monitoring - AWS has confirmed recovery of all their affected services. We are monitoring our services to ensure the services are back to normal. Feb 10, 22:35 UTC Update - We are continuing to investigate this issue with AWS as this may be affecting other regions (DCs/ Dashboards) due to issues in their global services like CloudFront. Feb 10, 22:10 UTC Investigating - We are currently experiencing a disruption affecting multiple services due to an ongoing outage with our cloud service provider, AWS. Our team is actively monitoring their status updates and collaborating with AWS to restore services as quickly as possible. For more details on AWS’s status, please visit: https://health.aws.amazon.com/health/status

Read the full incident report →

Started Jan 14, 2026, 05:53 PM UTC· resolved Jan 14, 2026, 05:53 PM UTC

1. resolved Jan 14, 2026, 05:53 PM UTC

   Jan 14, 17:53 UTC Resolved - This incident has been resolved. Jan 14, 17:49 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jan 14, 17:45 UTC Identified - We are currently experiencing a delay of approximately one hour for File and Warehouse Imports and Exports. Our engineering team has identified the root cause and is actively working on a resolution. We will provide further updates as soon as more information is available.

Read the full incident report →

Started Dec 23, 2025, 11:56 PM UTC· resolved Dec 23, 2025, 11:56 PM UTC

1. resolved Dec 23, 2025, 11:56 PM UTC

   Dec 23, 23:56 UTC Resolved - This incident has been resolved. Dec 23, 09:44 UTC Monitoring - We are currently experiencing degraded performance in our Stats system, resulting in delays of approximately one hour in updating campaign analytics and reports. Campaign sending and triggers remain fully operational — only the updating of statistics is affected. Our team has implemented a fix and is actively monitoring to ensure performance returns to normal. We apologize for any inconvenience this may cause and appreciate your patience while we continue to verify stability.

Read the full incident report →