Historial de interrupciones de Moengage

1. August 18, 2026 at 10:31 AM UTCresolved

   Resumen Entre 2026-08-17 a las 19:55 IST y 2026-08-18 a las 12:00 IST, un subconjunto de solicitudes hechas a la API de información puede no haberse entregado con éxito. Las solicitudes afectadas recibieron una respuesta HTTP 200 OK, indicando éxito, pero los mensajes correspondientes nunca fueron enviados. La cuestión se ha resuelto totalmente a partir de 2026-08-18 a las 12.00 horas. Impacto - Los clientes que utilizan la API de información enrutada a través de DC-03 durante la ventana afectada pueden haber sido afectados - Las solicitudes afectadas aparecieron exitosas en el lado cliente pero no fueron procesadas - En consecuencia, no se enviaron mensajes relacionados con esas solicitudes. - No podemos reiniciar o reproducir automáticamente las solicitudes afectadas Lo que hicimos Identificamos el problema durante una actualización interna rutinaria de enrutamiento y volamos inmediatamente el cambio. El servicio completo fue restaurado a las 2026-08-18 a las 12:00 IST. Lo que deberías hacer Si cree que su integración fue afectada durante esta ventana, le recomendamos: - Revisión de sus registros de solicitudes realizadas entre 2026-08-17 19:55 IST y 2026-08-18 12:00 IST - Identificar los mensajes que no fueron entregados como se esperaba - Re-sending those requests manually if delivery is still required Sinceramente nos disculpamos por las molestias que esto puede haber causado. Si tiene alguna pregunta o necesita ayuda para identificar las solicitudes afectadas, por favor contacte con nuestro equipo de apoyo.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 10:07 AM UTCinvestigating

   Actualmente estamos experimentando un rendimiento degradado en múltiples servicios. Nuestro equipo de ingeniería está investigando activamente la cuestión y trabajando para restaurar el servicio completo lo antes posible. Lo que sabemos tan lejos Múltiples servicios están experimentando rendimiento degradado Los canales de salida son particularmente impactados y algunos usuarios pueden experimentar retrasos o fracasos con la entrega de mensajes fuera de línea Nuestro equipo ha identificado un problema potencial con nuestra infraestructura de nube subyacente y está investigando activamente Lo que estamos haciendo Nuestro equipo de ingeniería está investigando activamente la causa raíz y está trabajando para restaurar el servicio completo. Compartiremos más detalles cuando estén disponibles. Proporcionaremos nuestra próxima actualización dentro de 30 minutos. Sinceramente nos disculpamos por la perturbación que esto puede causar a sus operaciones. Gracias por su paciencia y comprensión mientras trabajamos para resolver esto.

2. July 27, 2026 at 10:12 AM UTCinvestigating

   Hemos identificado que nuestros servidores están experimentando demoras en escalar dentro de nuestra infraestructura de nube. Esto está causando que el envío de campaña sea significativamente más lento de lo normal como resultado. Nuestro equipo de ingeniería está trabajando activamente en una resolución y proporcionaremos una nueva actualización en breve.

3. July 27, 2026 at 10:13 AM UTCinvestigating

   Las campañas y flujos desencadenados por el evento también están experimentando un rendimiento degradado. Nuestro equipo sigue trabajando en una resolución y proporcionaremos una nueva actualización en breve.

4. July 27, 2026 at 10:32 AM UTCinvestigating

   Nuestro equipo de ingeniería ha implementado un trabajo temporal que ha ayudado a mejorar el rendimiento. El envío de campañas se ha reanudado, sin embargo, puede que todavía experimente velocidades de entrega más lentas de lo habitual mientras seguimos trabajando en una resolución completa. Presentaremos una nueva actualización en breve.

5. July 27, 2026 at 11:07 AM UTCidentified

   Nuestro proveedor de infraestructura en la nube está experimentando problemas que están afectando nuestros servicios. Estamos en comunicación activa con ellos y estamos trabajando juntos para lograr una recuperación completa. Estamos viendo mejoras graduales y los servicios están empezando a recuperarse, sin embargo esto puede tomar algún tiempo. Agradecemos su paciencia continua mientras trabajamos hacia la plena resolución. Presentaremos una nueva actualización en breve.

6. July 27, 2026 at 11:38 AM UTCmonitoring

   Nos complace confirmar que nuestro equipo de ingeniería ha identificado la causa raíz y aplicado con éxito una solución. Nuestra infraestructura se ha recuperado rápidamente y estamos viendo una fuerte mejora en todos los servicios afectados. Los servicios han regresado a la normalidad y estamos en proceso de aclarar el retraso restante. Publicaremos una actualización final una vez que el atraso haya sido completamente aclarado. Gracias por su paciencia y comprensión durante todo este incidente.

7. July 27, 2026 at 2:47 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 25, 2026 at 9:11 AM UTCinvestigating

   Actualmente estamos investigando cuestiones relacionadas con los siguientes servicios en DC01: - Información - Campañas y flujos desencadenados por el evento

2. July 25, 2026 at 9:53 AM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 25, 2026 at 9:54 AM UTCinvestigating

   Seguimos trabajando en la mitigación.

4. July 25, 2026 at 11:36 AM UTCmonitoring

   Actualmente estamos monitoreando servicios

5. July 25, 2026 at 12:00 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 1, 2026 at 10:02 AM UTCresolved

   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.

1. June 4, 2026 at 10:17 AM UTCresolved

   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.

1. May 14, 2026 at 9:55 AM UTCinvestigating

   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. May 14, 2026 at 9:57 AM UTCmonitoring

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

3. May 14, 2026 at 11:35 AM UTCmonitoring

   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. May 14, 2026 at 3:01 PM UTCresolved

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

1. May 13, 2026 at 10:02 PM UTCmonitoring

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

2. May 14, 2026 at 3:39 AM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 4:35 AM UTCmonitoring

   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. April 24, 2026 at 5:27 AM UTCresolved

   This incident has been resolved.

1. April 20, 2026 at 10:34 AM UTCmonitoring

   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.

2. April 21, 2026 at 1:45 AM UTCresolved

   This incident has been resolved.

1. April 9, 2026 at 8:39 AM UTCresolved

   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.

1. March 31, 2026 at 11:11 AM UTCmonitoring

   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.

2. March 31, 2026 at 11:41 AM UTCresolved

   This incident has been resolved. The lag was observed from 06:45 UTC (12:15pm IST) to 11:30 UTC (05:00pm IST).

1. March 24, 2026 at 2:47 PM UTCidentified

   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.

2. March 24, 2026 at 3:54 PM UTCresolved

   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.

1. March 13, 2026 at 2:12 AM UTCinvestigating

   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.

2. March 13, 2026 at 2:13 AM UTCinvestigating

   We are continuing to investigate this issue.

3. March 13, 2026 at 2:32 AM UTCidentified

   The issue has been identified and a fix is being implemented.

4. March 13, 2026 at 3:11 AM UTCmonitoring

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

5. March 13, 2026 at 5:16 AM UTCresolved

   This incident has been resolved.

1. March 12, 2026 at 5:05 PM UTCidentified

   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.

2. March 12, 2026 at 7:18 PM UTCresolved

   This incident has been resolved.

1. March 6, 2026 at 10:56 AM UTCmonitoring

   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.

2. March 6, 2026 at 11:05 AM UTCmonitoring

   We are continuing to monitor for any further issues.

3. March 6, 2026 at 11:06 AM UTCresolved

   The incident has been resolved. The issue lasted for 30 min from 10:35 to 11:05 UTC.

1. March 5, 2026 at 3:28 PM UTCinvestigating

   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.

2. March 5, 2026 at 3:31 PM UTCidentified

   The issue has been identified and a fix is being implemented.

3. March 5, 2026 at 3:31 PM UTCidentified

   We are continuing to work on a fix for this issue.

4. March 5, 2026 at 4:29 PM UTCmonitoring

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

5. March 5, 2026 at 5:15 PM UTCresolved

   This incident has been resolved.

1. February 25, 2026 at 12:05 PM UTCinvestigating

   We are currently investigating the issue.

2. February 25, 2026 at 12:16 PM UTCmonitoring

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

3. February 25, 2026 at 12:18 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 4:12 PM UTCmonitoring

   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.

2. February 11, 2026 at 4:16 PM UTCmonitoring

   We are continuing to monitor for any further issues.

3. February 11, 2026 at 5:50 PM UTCresolved

   This incident has been resolved.

1. February 10, 2026 at 10:10 PM UTCinvestigating

   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

2. February 10, 2026 at 10:35 PM UTCinvestigating

   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.

3. February 10, 2026 at 10:52 PM UTCmonitoring

   AWS has confirmed recovery of all their affected services. We are monitoring our services to ensure the services are back to normal.

4. February 10, 2026 at 10:56 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. February 11, 2026 at 3:31 AM UTCresolved

   This incident has been resolved.

1. January 14, 2026 at 5:45 PM UTCidentified

   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.

2. January 14, 2026 at 5:49 PM UTCmonitoring

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

3. January 14, 2026 at 5:53 PM UTCresolved

   This incident has been resolved.