Istoricul incidentelor Moengage

1. 18 august 2026 la 10:31 UTCresolved

   Rezumat Intre 2026-08-17 la 19:55 IST si 2026-08-18 la 12:00 IST, un subset de cereri facute la API Informare nu au fost livrate cu succes. Cererile afectate au primit un răspuns HTTP 200 OK, indicând succesul, dar mesajele corespunzătoare nu au fost trimise niciodată. Problema a fost rezolvată pe deplin începând cu 2026-08-18 la ora 12:00 IST. Impact - Clientii care folosesc Informatii API rutate prin DC-03 in timpul ferestrei afectate pot fi afectate - Solicitările afectate par să aibă succes din partea clientului, dar nu au fost prelucrate - Ca rezultat, mesajele asociate cu aceste cereri nu au fost livrate - Nu putem rejudeca automat cererile afectate Ce am făcut Am identificat problema în timpul unei actualizări de rutină de rutare internă și imediat laminate înapoi schimbarea. Serviciul complet a fost restaurat la 2026-08-18 la 12:00 IST. Ce ar trebui să faci Dacă credeți că integrarea a fost afectată în timpul acestei ferestre, vă recomandăm: - Revizuirea jurnalelor pentru cererile făcute între 2026-08-17 19:55 IST şi 2026-08-18 12:00 IST - Identificarea mesajelor care nu au fost livrate conform aşteptărilor - Re-trimiterea acestor cereri manual, dacă livrarea este încă necesară Ne cerem sincer scuze pentru neplăcerile cauzate. Dacă aveți întrebări sau aveți nevoie de asistență pentru identificarea cererilor afectate, vă rugăm să contactați echipa noastră de sprijin.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 10:07 UTCinvestigating

   În prezent ne confruntăm cu performanțe degradate în cadrul mai multor servicii. Echipa noastră de inginerie investighează în mod activ problema și lucrează pentru a restabili serviciul complet cât mai repede posibil. Ceea ce ştim până acum Serviciile multiple se confruntă cu performanțe degradate Canalele outbound sunt deosebit de afectate și unii utilizatori pot experimenta întârzieri sau eșecuri cu livrarea de mesaje outbound Echipa noastră a identificat o potenţială problemă cu infrastructura noastră de cloud şi investighează activ Ce facem Echipa noastră de ingineri investighează în mod activ cauza principală și lucrează pentru a restabili serviciul complet. Vom împărtăși mai multe detalii pe măsură ce acestea devin disponibile. Vom furniza următoarea actualizare în 30 de minute. Ne cerem scuze sincer pentru întrerupere acest lucru poate fi cauza pentru operațiunile dumneavoastră. Vă mulțumim pentru răbdare și înțelegere în timp ce lucrăm pentru a rezolva acest lucru.

2. 27 iulie 2026 la 10:12 UTCinvestigating

   Am identificat că serverele noastre se confruntă cu întârzieri în extinderea infrastructurii noastre de cloud. Acest lucru determină ca trimiterea campaniei să fie semnificativ mai lentă decât este normal ca rezultat. Echipa noastră de inginerie lucrează activ la o rezoluție și vom oferi o actualizare în curând.

3. 27 iulie 2026 la 10:13 UTCinvestigating

   Campanie și fluxuri declanșate de evenimente se confruntă, de asemenea, cu performanțe degradate. Echipa noastră continuă să lucreze la o rezoluție și vom oferi o actualizare în curând.

4. 27 iulie 2026 la 10:32 UTCinvestigating

   Echipa noastră de ingineri a implementat un proces temporar care a contribuit la îmbunătăţirea performanţei. Trimiterea campaniei s-a reluat, însă s-ar putea să experimentați în continuare viteze mai lente decât de obicei, în timp ce continuăm să lucrăm la o rezoluție completă. Vom oferi o actualizare în curând.

5. 27 iulie 2026 la 11:07 UTCidentified

   Furnizorul nostru de infrastructuri de cloud se confruntă în prezent cu probleme care afectează serviciile noastre. Suntem în comunicare activă cu ei și lucrăm împreună pentru a obține o recuperare completă. Vedem îmbunătăţiri treptate şi servicii încep să-şi revină, însă acest lucru poate dura ceva timp. Apreciem răbdarea dvs. continuă în timp ce lucrăm pentru rezolvarea completă. Vom oferi o actualizare în curând.

6. 27 iulie 2026 la 11:38 UTCmonitoring

   Suntem încântaţi să confirmăm că echipa noastră de inginerie a identificat cauza principală şi a aplicat cu succes un fix. Infrastructura noastră s-a redresat rapid şi vedem îmbunătăţiri puternice în toate serviciile afectate. Serviciile au revenit la normal și suntem în proces de compensare a resturilor. Vom posta o actualizare finală odată ce registrul a fost complet șters. Vă mulțumim pentru răbdare și înțelegere pe parcursul acestui incident.

7. 27 iulie 2026 la 14:47 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 25 iulie 2026 la 09:11 UTCinvestigating

   Investigăm în prezent o problemă legată de următoarele servicii din DC01: - Informează - Evenimente declanşate campanii şi flux

2. 25 iulie 2026 la 09:53 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 25 iulie 2026 la 09:54 UTCinvestigating

   Continuăm să lucrăm la atenuare.

4. 25 iulie 2026 la 11:36 UTCmonitoring

   În prezent monitorizăm serviciile

5. 25 iulie 2026 la 12:00 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 1 iunie 2026 la 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 iunie 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 03:39 UTCresolved

   This incident has been resolved.

1. 24 aprilie 2026 la 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 aprilie 2026 la 05:27 UTCresolved

   This incident has been resolved.

1. 20 aprilie 2026 la 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 aprilie 2026 la 01:45 UTCresolved

   This incident has been resolved.

1. 9 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 02:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 13 martie 2026 la 02:32 UTCidentified

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

4. 13 martie 2026 la 03:11 UTCmonitoring

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

5. 13 martie 2026 la 05:16 UTCresolved

   This incident has been resolved.

1. 12 martie 2026 la 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 martie 2026 la 19:18 UTCresolved

   This incident has been resolved.

1. 6 martie 2026 la 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 martie 2026 la 11:05 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 6 martie 2026 la 11:06 UTCresolved

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

1. 5 martie 2026 la 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 martie 2026 la 15:31 UTCidentified

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

3. 5 martie 2026 la 15:31 UTCidentified

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

4. 5 martie 2026 la 16:29 UTCmonitoring

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

5. 5 martie 2026 la 17:15 UTCresolved

   This incident has been resolved.

1. 25 februarie 2026 la 12:05 UTCinvestigating

   We are currently investigating the issue.

2. 25 februarie 2026 la 12:16 UTCmonitoring

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

3. 25 februarie 2026 la 12:18 UTCresolved

   This incident has been resolved.

1. 11 februarie 2026 la 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 februarie 2026 la 16:16 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 11 februarie 2026 la 17:50 UTCresolved

   This incident has been resolved.

1. 10 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 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 februarie 2026 la 22:56 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 11 februarie 2026 la 03:31 UTCresolved

   This incident has been resolved.

1. 14 ianuarie 2026 la 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 ianuarie 2026 la 17:49 UTCmonitoring

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

3. 14 ianuarie 2026 la 17:53 UTCresolved

   This incident has been resolved.