Moengage 中断历史

1. 2026年10月28日 UTC 08:38identified

   我们正面临关闭 仪表板登录和注册 通过Google Auth 在所有Dashboard上。 我们已经确定了这一问题,小组正在积极努力解决这个问题.

2. 2026年10月28日 UTC 09:01resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年10月28日 UTC 08:06monitoring

   我们在处理 " 运动参与 " 统计时,看到业绩下降,包括印象,打开、点击和喜欢。 这个问题已经解决,我们正在积极监测这一制度。 然而,随着处理工作恢复正常,30多分钟的拖延可能持续了一段时间。 运动发送和交付统计数据没有受到影响。 我们为不便而道歉,并感谢你的耐心.

2. 2026年10月28日 UTC 10:31resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年10月27日 UTC 02:20investigating

   Push API 目前正经历整个数据中心的故障,导致请求失败或被延迟。 我们的小组正在积极调查这个问题并努力安全恢复服务。 随着调试和获得更多信息,我们将不断更新。 我们为干扰道歉 并感谢你的耐心.

2. 2026年10月27日 UTC 03:13investigating

   V1运动API也在我们的数据中心经历同样的故障时间,导致请求失败或被延迟.

3. 2026年10月27日 UTC 03:28investigating

   我们建议同时从MoEngage仪表板上发起运动。 已经建立和开展的运动不受影响。 一旦掌握更多信息,我们将立即分享最新情况。 我们为不方便而道歉.

4. 2026年10月27日 UTC 03:29investigating

   目前,我们与 " API V1运动 " 一起开展创建运动,服务正在退化。 通过该API创建运动的请求可能失败或被拒绝. 我们建议同时从MoEngage仪表板上发起运动。 已经建立和开展的运动不受影响。 一旦掌握更多信息,我们将立即分享最新情况。 我们为不方便而道歉.

5. 2026年10月27日 UTC 12:39identified

   个人用户发送的 Push API 已被恢复到所有用户. 我们的小组继续努力恢复剩余的受影响服务。 我们将在获得更多信息后提供进一步的最新资料。 谢谢你的耐心.

6. 2026年10月27日 UTC 13:23identified

   Push API面向所有用户和自定义分区发送的已恢复. 我们的团队继续努力恢复V1运动。 已经建立和开展的现有运动仍未受到影响。 我们将在获得更多信息后提供进一步的最新资料。 谢谢你的耐心.

7. 2026年10月27日 UTC 14:14resolved

   Campaigns v1 API恢复正常运作,事件现已解决. 谢谢你的耐心.

自动翻译自官方事件更新。

1. 2026年10月20日 UTC 08:43investigating

   包括我们的文献和知识库https://mogreat.com/docs。 我们的小组正在积极调查,并努力尽快恢复准入。 MoEngage仪表板,APIs,SDKs,以及运动投放都不受影响.

2. 2026年10月20日 UTC 11:12investigating

   我们正在继续调查这个问题。

3. 2026年10月20日 UTC 13:03resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年9月24日 UTC 11:39investigating

   我们正在调查一个影响 运动列表页面 在仪表板上。 一些用户在加载或查看其活动列表时可能会看到间歇性错误. 我们的工程小组正在积极进行这项工作,我们将在30分钟内或一旦获得更多信息,就分享下一次更新.

2. 2026年9月24日 UTC 11:48monitoring

   我们正在积极监测一个修复.

3. 2026年9月24日 UTC 12:23resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月18日 UTC 10:31resolved

   内容提要 在2026-08-17 : 19:55 IST和2026-08-18 : 12:00 IST之间,向信息API提出的一组请求可能没有成功交付. 受影响的请求收到HTTP 200 OK回复,表示成功,但相应的消息从未发出. 该问题自2026-08-18起已全部解决,时间为IST中午12点. 影响 - 在受影响的窗口内使用通过DC-03传送的信息API的客户可能受到影响 - 受影响请求在客户方面似乎成功,但没有处理 - 因此,与这些请求有关的信息没有发出 - 我们无法自动重试或重放受影响的请求 我们所做的 我们在例行的内部线路更新中确定了这一问题,并立即回滚了变化。 2026-08-18 12:00 IST恢复了全程服务. 你该做什么? 如果你认为你的融合在这个窗口里受到影响,我们建议: - 审查2026-08-17 19:55 IST和2026-08-18 中午12:00 IST之间的申请记录 - 查明未按预期发送的任何信息 - 如果仍然需要交付,则手动重新发送这些请求 我们对此可能造成的不便表示诚挚的歉意。 如有问题或需要协助确定受影响请求,请联系我们的支助小组.

自动翻译自官方事件更新。

1. 2026年7月27日 UTC 10:07investigating

   目前,我们在多种服务领域的业绩正在退化。 我们的工程组正在积极调查这个问题,并努力尽快恢复全面服务. 我们所知如此之远 多种服务的业绩正在退化 外出渠道尤其受到影响,一些用户在外出发送信息时可能遇到延误或故障 我们的团队已经找出一个潜在的问题 我们潜在的云层基础设施 并正在积极调查 我们在做什么 我们的工程组正在积极调查根源,并正努力恢复全面服务。 详细情况一旦公布,我们将予以通报。 我们将在30分钟内提供下一次最新情况。 我们诚恳地为这可能会对你们的行动造成干扰而道歉。 在我们努力解决这个问题时,感谢你的耐心和理解.

2. 2026年7月27日 UTC 10:12investigating

   我们发现,我们的服务器在云基础设施内扩大规模方面出现延误。 这使得竞选的送出速度大大低于正常. 我们的工程队正在积极拟订一项决议,我们将很快提供进一步的最新资料.

3. 2026年7月27日 UTC 10:13investigating

   事件触发运动和流动也出现业绩下降。 我们的小组继续就一项决议开展工作,我们将很快提供进一步的最新情况.

4. 2026年7月27日 UTC 10:32investigating

   我们的工程队进行了临时工作,帮助提高了业绩。 运动已经恢复,然而,在我们继续努力全面解决问题的同时,你们仍然可能比通常的交付速度慢。 我们不久将提供进一步的最新情况.

5. 2026年7月27日 UTC 11:07identified

   我们的云基础设施供应商目前正在经历影响我们服务的问题。 我们正在同它们积极沟通,并正在共同努力实现全面恢复。 我们看到逐步改善,服务开始恢复,但可能需要一些时间。 我们赞赏你继续耐心地努力争取全面解决。 我们不久将提供进一步的最新情况.

6. 2026年7月27日 UTC 11:38monitoring

   我们高兴地确认,我们的工程队已经查明了根源,并成功地采取了补救措施。 我们的基础设施已迅速恢复,我们看到所有受影响的服务都有了很大的改善。 服务已恢复正常,我们正在清理剩余的积压。 一旦积压工作全部清理完毕,我们将公布最后最新情况。 感谢你在整个事件中的耐心和理解.

7. 2026年7月27日 UTC 14:47resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月25日 UTC 09:11investigating

   我们目前正在调查DC01中与下列服务有关的问题: - 通报 - 事件触发运动和流动

2. 2026年7月25日 UTC 09:53investigating

   我们正在继续调查这一问题.

3. 2026年7月25日 UTC 09:54investigating

   我们继续就减缓问题开展工作.

4. 2026年7月25日 UTC 11:36monitoring

   我们目前正在监测服务

5. 2026年7月25日 UTC 12:00resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年6月1日 UTC 10:02resolved

   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日 UTC 10:17resolved

   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日 UTC 09:55investigating

   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日 UTC 09:57monitoring

   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日 UTC 11:35monitoring

   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日 UTC 15:01resolved

   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日 UTC 22:02monitoring

   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日 UTC 03:39resolved

   This incident has been resolved.

1. 2026年4月24日 UTC 04:35monitoring

   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日 UTC 05:27resolved

   This incident has been resolved.

1. 2026年4月20日 UTC 10:34monitoring

   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日 UTC 01:45resolved

   This incident has been resolved.

1. 2026年4月9日 UTC 08:39resolved

   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日 UTC 11:11monitoring

   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日 UTC 11:41resolved

   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日 UTC 14:47identified

   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日 UTC 15:54resolved

   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日 UTC 02:12investigating

   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日 UTC 02:13investigating

   We are continuing to investigate this issue.

3. 2026年3月13日 UTC 02:32identified

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

4. 2026年3月13日 UTC 03:11monitoring

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

5. 2026年3月13日 UTC 05:16resolved

   This incident has been resolved.

1. 2026年3月12日 UTC 17:05identified

   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日 UTC 19:18resolved

   This incident has been resolved.

1. 2026年3月6日 UTC 10:56monitoring

   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日 UTC 11:05monitoring

   We are continuing to monitor for any further issues.

3. 2026年3月6日 UTC 11:06resolved

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