Public Cloud incident
[Global][PCI-Databases] - MongoDB incident notification
Public Cloud experienced a minor incident on June 4, 2026 affecting BHS and DE and 1 more component, lasting 20h 57m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 04, 2026, 09:28 AM UTC
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 : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. Ongoing Actions : 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.
- identified Jun 04, 2026, 09:33 AM UTC
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 : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially run with 3 nodes may temporarily run with 2 nodes. Customers Impact : Customers with 3 node MongoDB services may temporarily operate with only 2 nodes. No latency or data loss is observed. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. Ongoing Actions : 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.
- monitoring Jun 04, 2026, 12:07 PM UTC
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 : Start time : 03/06/2026 12:00 UTC Impacted Service(s) : Some MongoDB databases that initially ran with 3 nodes temporarily ran with 2 nodes Customers Impact : Customers with 3-node MongoDB services temporarily operated with only 2 nodes. No latency or data loss was observed Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
- resolved Jun 05, 2026, 06:26 AM UTC
We are pleased to inform you that the incident affecting our PCI-Databases offering has been resolved. Start time : 03/06/2026 12:00 UTC End time : 04/06/2026 12:00 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.