Moengage 장애 기록

1. 2026년 8월 18일 AM 10:31 UTCresolved

   제품정보 2026-08-17 사이 19:55 IST 및 2026-08-18 12:00 IST, Inform API로 만든 요청의 하위 세트가 성공적으로 전달되지 않을 수 있습니다. Affected 요청은 HTTP 200 OK 응답을 받았다, 성공 나타내는, 하지만 해당 메시지는 결코 전송되지 않았다. 문제는 12:00 IST에서 2026-08-18로 완전히 해결되었습니다. 제품 정보 - 영향을받는 창 중 DC-03를 통해 Inform API를 사용하는 고객은 영향을 미칠 수 있습니다. - Affected 요청은 클라이언트 측에 성공했지만 처리되지 않았습니다. - 그 요청과 관련된 메시지는 전달되지 않았습니다. - 우리는 자동으로 재발하거나 영향을받는 요청을 재생할 수 없습니다. 우리가 하는 것 우리는 일상적인 내부 routing 갱신 도중 문제점을 확인하고 즉시 변화를 구출했습니다. 전체 서비스는 12:00 IST에서 2026-08-18에 복원되었습니다. 당신이해야 할 일 이 창에서 통합이 영향을받는 것을 믿는다면, 우리는 추천합니다: - 2026-08-17 19:55 IST 및 2026-08-18 12:00 IST 사이에 요청된 로그 검토 - 예상대로 전달되지 않은 모든 메시지 식별 - 배송이 여전히 필요한 경우 해당 요청을 수동으로 다시 종료 우리는 진심으로 불편을 끼쳐 드려 죄송합니다. 어떤 질문이나 도움이 필요하면 영향을받는 요청을 식별 할 수 있습니다. 지원 팀에 도달하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 27일 AM 10:07 UTCinvestigating

   우리는 현재 다수 서비스의 맞은편에 degraded 성과를 경험하고 있습니다. 우리의 엔지니어링 팀은 적극적으로 문제를 투자하고 가능한 한 빨리 전체 서비스를 복원 작업. 우리가 알고있는 일 다수 서비스는 degraded 성과를 경험하고 있습니다 아웃바운드 채널은 특히 충격 및 일부 사용자는 아웃바운드 메시지 전달과 지연 또는 실패를 경험할 수 있습니다. 우리의 팀은 우리의 underlying 클라우드 인프라와 잠재적 인 문제를 식별하고 적극적으로 조사 우리가 할 일 우리의 엔지니어링 팀은 뿌리 원인을 적극적으로 투자하고 전체 서비스를 복원하기 위해 노력하고 있습니다. 우리는 그들이 가능한 한 더 많은 정보를 공유 할 것입니다. 우리는 30 분 안에 우리의 다음 갱신을 제공할 것입니다. 우리는 진심으로 혼란에 대한 사과가이 작업을 일으킬 수 있습니다. 우리가 이것을 해결하기 위해 노력하는 동안 당신의 인내와 이해에 감사드립니다.

2. 2026년 7월 27일 AM 10:12 UTCinvestigating

   우리는 우리의 서버가 우리의 클라우드 인프라 내에서 스케일링 지연을 경험한다는 것을 확인했습니다. 이것은 결과로서 정상적인 것보다 훨씬 느리게 전송하는 캠페인이 발생합니다. 우리의 기술설계 팀은 해결책에 적극적으로 일하고 우리는 더 짧은 갱신을 제공할 것입니다.

3. 2026년 7월 27일 AM 10:13 UTCinvestigating

   Event Triggered Campaigns and Flows는 등급의 성능을 경험하고 있습니다. 우리의 팀은 해결책에 계속 일하고 우리는 더 짧은 갱신을 제공할 것입니다.

4. 2026년 7월 27일 AM 10:32 UTCinvestigating

   우리의 엔지니어링 팀은 성능 향상을 도왔습니다. 캠페인 전송은 재시작했지만, 보통 배달 속도보다 느리게 경험할 수 있지만 전체 해상도에서 계속 작동합니다. 더 많은 업데이트가 곧 제공됩니다.

5. 2026년 7월 27일 AM 11:07 UTCidentified

   우리의 클라우드 인프라 제공 업체는 현재 우리의 서비스에 영향을 미치는 문제점을 경험하고 있습니다. 우리는 그(것)들을 가진 활동적인 커뮤니케이션에 있고 가득 차있는 회복을 달성하기 위하여 함께 일하고 있습니다. 우리는 gradual 개선과 서비스가 복구되기 시작합니다. 그러나이 시간이 걸릴 수 있습니다. 우리는 우리가 풀 해결책을 향해 일하는 동안 지속적인 인내력을 평가합니다. 더 많은 업데이트가 곧 제공됩니다.

6. 2026년 7월 27일 AM 11:38 UTCmonitoring

   우리는 우리의 기술설계 팀이 뿌리 원인을 확인하고 성공적으로 고침을 적용한 것을 확인하기 위하여 만족됩니다. 우리의 인프라는 신속하게 회복하고 우리는 모든 영향을받는 서비스를 통해 강력한 개선을보고 있습니다. 서비스는 정상으로 돌아가고 나머지 backlog를 정리하는 과정에서 있습니다. 우리는 backlog가 완전히 명확하게되면 최종 업데이트를 게시합니다. 이 사건을 통해 인내 및 이해에 감사드립니다.

7. 2026년 7월 27일 PM 2:47 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 25일 AM 9:11 UTCinvestigating

   우리는 현재 DC01의 다음 서비스 관련 문제 조사: - 정보 - 이벤트 트리거 캠페인 및 흐름

2. 2026년 7월 25일 AM 9:53 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 7월 25일 AM 9:54 UTCinvestigating

   우리는 완화에 계속 노력합니다.

4. 2026년 7월 25일 AM 11:36 UTCmonitoring

   우리는 현재 서비스 모니터링

5. 2026년 7월 25일 PM 12:00 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 1일 AM 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. 2026년 6월 4일 AM 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. 2026년 5월 14일 AM 9: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. 2026년 5월 14일 AM 9:57 UTCmonitoring

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

3. 2026년 5월 14일 AM 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. 2026년 5월 14일 PM 3: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. 2026년 5월 13일 PM 10: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. 2026년 5월 14일 AM 3:39 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 AM 4: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. 2026년 4월 24일 AM 5:27 UTCresolved

   This incident has been resolved.

1. 2026년 4월 20일 AM 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. 2026년 4월 21일 AM 1:45 UTCresolved

   This incident has been resolved.

1. 2026년 4월 9일 AM 8: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. 2026년 3월 31일 AM 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. 2026년 3월 31일 AM 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. 2026년 3월 24일 PM 2: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. 2026년 3월 24일 PM 3: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. 2026년 3월 13일 AM 2: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. 2026년 3월 13일 AM 2:13 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 13일 AM 2:32 UTCidentified

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

4. 2026년 3월 13일 AM 3:11 UTCmonitoring

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

5. 2026년 3월 13일 AM 5:16 UTCresolved

   This incident has been resolved.

1. 2026년 3월 12일 PM 5: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. 2026년 3월 12일 PM 7:18 UTCresolved

   This incident has been resolved.

1. 2026년 3월 6일 AM 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. 2026년 3월 6일 AM 11:05 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2026년 3월 6일 AM 11:06 UTCresolved

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

1. 2026년 3월 5일 PM 3: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. 2026년 3월 5일 PM 3:31 UTCidentified

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

3. 2026년 3월 5일 PM 3:31 UTCidentified

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

4. 2026년 3월 5일 PM 4:29 UTCmonitoring

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

5. 2026년 3월 5일 PM 5:15 UTCresolved

   This incident has been resolved.

1. 2026년 2월 25일 PM 12:05 UTCinvestigating

   We are currently investigating the issue.

2. 2026년 2월 25일 PM 12:16 UTCmonitoring

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

3. 2026년 2월 25일 PM 12:18 UTCresolved

   This incident has been resolved.

1. 2026년 2월 11일 PM 4: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. 2026년 2월 11일 PM 4:16 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2026년 2월 11일 PM 5:50 UTCresolved

   This incident has been resolved.

1. 2026년 2월 10일 PM 10: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. 2026년 2월 10일 PM 10: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. 2026년 2월 10일 PM 10: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. 2026년 2월 10일 PM 10:56 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2026년 2월 11일 AM 3:31 UTCresolved

   This incident has been resolved.

1. 2026년 1월 14일 PM 5: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. 2026년 1월 14일 PM 5:49 UTCmonitoring

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

3. 2026년 1월 14일 PM 5:53 UTCresolved

   This incident has been resolved.