Histórico de interrupções do Moengage

1. 18 Eost 2026 da 10:31 UTCresolved

   Resumo Entre 2026-08-17 às 19:55 IST e 2026-08-18 às 12:00 IST, um subconjunto de pedidos feitos à API Informar pode não ter sido entregue com sucesso. Os pedidos afetados receberam uma resposta HTTP 200 OK, indicando sucesso, mas as mensagens correspondentes nunca foram enviadas. A questão foi totalmente resolvida a partir de 2026-08-18 às 12:00 IST. Impacto - Os clientes que usam o Inform API roteado através de DC-03 durante a janela afetada podem ter sido impactados - Pedidos afetados apareceram bem sucedidos do lado do cliente, mas não foram processados - Como resultado, as mensagens associadas a esses pedidos não foram entregues - Nós somos incapazes de tentar ou reproduzir automaticamente os pedidos afetados O Que Fizemos Identificamos o problema durante uma atualização de roteamento interno de rotina e imediatamente retrocedemos a mudança. O serviço completo foi restaurado em 2026-08-18 às 12:00 IST. O que você deve fazer Se você acredita que sua integração foi afetada durante esta janela, recomendamos: - Revisão de seus registros para pedidos feitos entre 2026-08-17 19:55 IST e 2026-08-18 12:00 IST - Identificar as mensagens que não foram entregues como esperado - Reenviar esses pedidos manualmente se a entrega ainda é necessária Pedimos sinceras desculpas pelo inconveniente que isso pode ter causado. Se você tiver alguma dúvida ou precisar de assistência para identificar pedidos afetados, por favor, contate nossa equipe de suporte.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 10:07 UTCinvestigating

   Atualmente estamos experimentando desempenho degradado em vários serviços. Nossa equipe de engenharia está ativamente investigando o problema e trabalhando para restaurar o serviço completo o mais rápido possível. O que sabemos até agora Vários serviços estão experimentando desempenho degradado Os canais de saída são particularmente impactados e alguns usuários podem sofrer atrasos ou falhas com a entrega de mensagens de saída Nossa equipe identificou um problema potencial com nossa infraestrutura de nuvem subjacente e está investigando ativamente O que estamos fazendo Nossa equipe de engenharia está ativamente investigando a causa raiz e está trabalhando para restaurar o serviço completo. Partilharemos mais detalhes à medida que estiverem disponíveis. Forneceremos nossa próxima atualização dentro de 30 minutos. Pedimos sinceras desculpas pela interrupção que isto pode estar a causar às vossas operações. Obrigado por sua paciência e compreensão enquanto trabalhamos para resolver isso.

2. 27 Gouere 2026 da 10:12 UTCinvestigating

   Identificamos que nossos servidores estão passando por atrasos na ampliação da nossa infraestrutura na nuvem. Isto está fazendo com que o envio de campanha seja significativamente mais lento do que o normal como resultado. Nossa equipe de engenharia está trabalhando ativamente em uma resolução e forneceremos uma nova atualização em breve.

3. 27 Gouere 2026 da 10:13 UTCinvestigating

   Campanhas e fluxos desencadeados por eventos também estão experimentando desempenho degradado. A nossa equipa continua a trabalhar numa resolução e vamos apresentar uma nova actualização em breve.

4. 27 Gouere 2026 da 10:32 UTCinvestigating

   Nossa equipe de engenharia implementou uma solução temporária que ajudou a melhorar o desempenho. O envio da campanha foi retomado, no entanto você ainda pode experimentar velocidades de entrega mais lentas do que as habituais enquanto continuamos a trabalhar em uma resolução completa. Providenciaremos uma nova atualização em breve.

5. 27 Gouere 2026 da 11:07 UTCidentified

   Nosso provedor de infraestrutura em nuvem está atualmente enfrentando problemas que estão impactando nossos serviços. Estamos em comunicação ativa com eles e estamos trabalhando juntos para alcançar uma recuperação completa. Estamos a ver melhorias graduais e os serviços estão a começar a recuperar, mas isto pode demorar algum tempo. Agradecemos a sua paciência enquanto trabalhamos para uma resolução completa. Providenciaremos uma nova atualização em breve.

6. 27 Gouere 2026 da 11:38 UTCmonitoring

   Temos o prazer de confirmar que nossa equipe de engenharia identificou a causa raiz e aplicou com sucesso uma correção. A nossa infra-estrutura recuperou rapidamente e estamos a ver uma forte melhoria em todos os serviços afectados. Os serviços voltaram ao normal e estamos no processo de limpar o atraso restante. Publicaremos uma atualização final assim que o backlog estiver totalmente limpo. Obrigado pela vossa paciência e compreensão durante todo este incidente.

7. 27 Gouere 2026 da 14:47 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 25 Gouere 2026 da 09:11 UTCinvestigating

   Atualmente estamos investigando questões relacionadas aos seguintes serviços em DC01: - Informar - Campanhas e fluxo desencadeados pelo evento

2. 25 Gouere 2026 da 09:53 UTCinvestigating

   Continuamos a investigar esta questão.

3. 25 Gouere 2026 da 09:54 UTCinvestigating

   Continuamos a trabalhar em mitigação.

4. 25 Gouere 2026 da 11:36 UTCmonitoring

   Estamos actualmente a monitorizar os serviços

5. 25 Gouere 2026 da 12:00 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Mezheven 2026 da 10:02 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. 4 Mezheven 2026 da 10:17 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. 14 Mae 2026 da 09:55 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. 14 Mae 2026 da 09:57 UTCmonitoring

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

3. 14 Mae 2026 da 11:35 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. 14 Mae 2026 da 15:01 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. 13 Mae 2026 da 22:02 UTCmonitoring

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

2. 14 Mae 2026 da 03:39 UTCresolved

   This incident has been resolved.

1. 24 Ebrel 2026 da 04:35 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. 24 Ebrel 2026 da 05:27 UTCresolved

   This incident has been resolved.

1. 20 Ebrel 2026 da 10:34 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. 21 Ebrel 2026 da 01:45 UTCresolved

   This incident has been resolved.

1. 9 Ebrel 2026 da 08:39 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. 31 Meurzh 2026 da 11:11 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. 31 Meurzh 2026 da 11:41 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. 24 Meurzh 2026 da 14:47 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. 24 Meurzh 2026 da 15:54 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. 13 Meurzh 2026 da 02:12 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. 13 Meurzh 2026 da 02:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 Meurzh 2026 da 02:32 UTCidentified

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

4. 13 Meurzh 2026 da 03:11 UTCmonitoring

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

5. 13 Meurzh 2026 da 05:16 UTCresolved

   This incident has been resolved.

1. 12 Meurzh 2026 da 17:05 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. 12 Meurzh 2026 da 19:18 UTCresolved

   This incident has been resolved.

1. 6 Meurzh 2026 da 10:56 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. 6 Meurzh 2026 da 11:05 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 6 Meurzh 2026 da 11:06 UTCresolved

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

1. 5 Meurzh 2026 da 15:28 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. 5 Meurzh 2026 da 15:31 UTCidentified

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

3. 5 Meurzh 2026 da 15:31 UTCidentified

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

4. 5 Meurzh 2026 da 16:29 UTCmonitoring

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

5. 5 Meurzh 2026 da 17:15 UTCresolved

   This incident has been resolved.

1. 25 Cʼhwevrer 2026 da 12:05 UTCinvestigating

   We are currently investigating the issue.

2. 25 Cʼhwevrer 2026 da 12:16 UTCmonitoring

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

3. 25 Cʼhwevrer 2026 da 12:18 UTCresolved

   This incident has been resolved.

1. 11 Cʼhwevrer 2026 da 16:12 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. 11 Cʼhwevrer 2026 da 16:16 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 11 Cʼhwevrer 2026 da 17:50 UTCresolved

   This incident has been resolved.

1. 10 Cʼhwevrer 2026 da 22:10 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. 10 Cʼhwevrer 2026 da 22:35 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. 10 Cʼhwevrer 2026 da 22:52 UTCmonitoring

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

4. 10 Cʼhwevrer 2026 da 22:56 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 11 Cʼhwevrer 2026 da 03:31 UTCresolved

   This incident has been resolved.

1. 14 Genver 2026 da 17:45 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. 14 Genver 2026 da 17:49 UTCmonitoring

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

3. 14 Genver 2026 da 17:53 UTCresolved

   This incident has been resolved.