MoEngage Outage History

30 incidents recorded over the last 365 days, 27 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live MoEngage status100.00% uptime history

Every Recorded MoEngage Incident

MoEngage incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Dashboard Login and Sign-Ups via Google failingThis incident has been resolved.23 minResolved
Oct 28, 2026Dashboard-04 – Campaign Engagement Statistics DelayedThis incident has been resolved.2h 25mResolved
Oct 27, 2026Campaigns v1 and Push API Service DisruptionThe Campaigns v1 API has been restored to normal operation, and the incident is now resolved. Thank you for your patience.11h 54mResolved
Oct 23, 2026Dashboard MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Oct 20, 2026https://moengage.com/docs experiencing issuesThis incident has been resolved.4h 19mResolved
Sep 24, 2026DC01 - Campaigns Dashboard is experiencing intermittent errorsThis incident has been resolved.43 minResolved
Sep 3, 2026DC 01 | Aux User-Profile Data MigrationThe scheduled maintenance has been completed.4h 30mScheduled
Aug 18, 2026Dashboard 03 — Inform API: Some Messages Not Delivered During Routing UpdateSummary Between 2026-08-17 at 19:55 IST and 2026-08-18 at 12:00 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…-1201 minResolved
Jul 27, 2026Dashboard 01 - Degraded Performance Across Multiple ServicesThis incident has been resolved.4h 40mResolved
Jul 25, 2026DC01 - Degraded performance of Inform, Event Triggered Campaigns, FlowsThis incident has been resolved.2h 49mResolved
Jun 1, 2026Dashboard 02 - Degradation in Email Link Branding ServiceBetween 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…-302 minResolved
Jun 1, 2026Dashboard 02 and 04 - Email Delivery Reporting ImpactOn 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 —…0 minResolved
May 14, 2026DC03 | Delay in data ingestionThe lag is cleared and latency is within our SLA threshold. The team will take corrective actions as part of the incident post mortem.5h 6mResolved
May 13, 2026DC04 | Delay in Data ProcessingThis incident has been resolved.5h 37mResolved
Apr 24, 2026[Dashboard-02] Delay in Campaign SendingThis incident has been resolved.51 minResolved
Apr 20, 2026Dashboard 01 - Degraded Performance in Data IngestionThis incident has been resolved.15h 11mResolved
Apr 9, 2026DC03 | Lag in data ingestionThere 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…0 minResolved
Mar 31, 2026Dashboard 03 – Degraded Performance in Trigger-Based FlowsThis incident has been resolved. The lag was observed from 06:45 UTC (12:15pm IST) to 11:30 UTC (05:00pm IST).29 minResolved
Mar 24, 2026[Dashboard-03] Delay in Ingestion PipelineThe 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…0 minResolved
Mar 13, 2026Dashboard-03 Service Impact -Smart Trigger and Flow CampaignsThis incident has been resolved.3h 4mResolved
Mar 12, 2026Dc03 | Data ingestion lag | Event processingThis incident has been resolved.2h 13mResolved
Mar 6, 2026[Dashboard-02] All Campaigns Page not loadingThe incident has been resolved. The issue lasted for 30 min from 10:35 to 11:05 UTC.9 minResolved
Mar 5, 2026Dashboard 03 - Delay in Stats updateThis incident has been resolved.1h 46mResolved
Feb 25, 2026[Dashboard-03] Dashboard not loadingThis incident has been resolved.13 minResolved
Feb 19, 2026DC01 - Scheduled Infrastructure Maintenance Notice: Resizing of Data ClustersThe scheduled maintenance has been completed.3h 0mScheduled
Feb 11, 2026[Dashboard-02] Delay in processing Data Imports & ExportsThis incident has been resolved.1h 38mResolved
Feb 10, 2026Service OutageThis incident has been resolved.5h 20mResolved
Jan 14, 2026[DC-04] - Delay in File and Warehouse ProcessingThis incident has been resolved.7 minResolved
Jan 12, 2026Dashboard 03 - Delay in Stats updateThis incident has been resolved.34h 19mResolved
Dec 23, 2025Dashboard-03 : Degraded Performance in Stats ProcessingThis incident has been resolved.14h 12mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next MoEngage incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This MoEngage Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before MoEngage acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single MoEngage outage in this window ran 1d 10h, against a mean recovery of 4h 30m. If you depend on MoEngage in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.