Skip to content

Incident detail

[Global][PCI-Databases] - MongoDB incident notification

[Global][PCI-Databases] - MongoDB incident notification

Resolved incidentMinor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary degraded issue in the Global region. Here are some supplementary details : <b>Start time :</b> 03/06/2026 12:00 UTC <b>Impacted Service(s) :</b> Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. <b>Customers Impact :</b> Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. <b>Ongoing Actions :</b> Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  2. Identified

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PCI-Databases offer on the specific global region. Here are some supplementary details : <b>Start time :</b> 03/06/2026 12:00 UTC <b>Impacted Service(s) :</b> Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. <b>Customers Impact :</b> Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. Monitoring

    Service has been fully restored since 04/06/2026 12:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 03/06/2026 12:00 UTC <b>Impacted Service(s) :</b> Some MongoDB databases that initially ran with 3 nodes temporarily ran with 2 nodes <b>Customers Impact :</b> Customers with 3-node MongoDB services temporarily operated with only 2 nodes. No latency or data loss was observed <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  4. Resolved

    We are pleased to inform you that the incident affecting our PCI-Databases offering has been resolved. <b>Start time :</b> 03/06/2026 12:00 UTC <b>End time :</b> 04/06/2026 12:00 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.