Live  /  MoEngage  /  Incident

MoEngage: Campaigns v1 and Push API Service Disruption

MoEngage · moengage.comMajor incidentResolved2026-10-27 14:14 UTC
Public — what happened

Summary

MoEngage said its Push API went down across its data centers starting at 02:20 UTC on 2026-10-27, causing requests to fail or be delayed. About an hour later it reported that the Campaigns v1 API had the same problem, and advised customers to create campaigns from the dashboard instead, noting that campaigns already running were not affected. Push sends to individual users were restored at 12:39 UTC, and sends to all users and custom segments followed at 13:23 UTC, while work continued on Campaigns v1. The incident was marked resolved at 14:14 UTC, and the text provided does not name a cause.

Affected

Push APIs, Push APIs, Push APIs, Push APIs, Push APIs, Push APIs, Push APIs

As listed on MoEngage’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach MoEngage against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for MoEngage: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the MoEngage report →

More from MoEngage

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the MoEngage status & history page.

Related: MoEngage status & history. SquidGrid is not affiliated with MoEngage.