Public Cloud incident

[GRA][Databases] - MongoDB Discovery incident notification

Major Resolved View vendor source →

Public Cloud experienced a major incident on March 12, 2026 affecting GRA, lasting 3d 23h. The incident has been resolved; the full update timeline is below.

Started
Mar 12, 2026, 09:33 AM UTC
Resolved
Mar 16, 2026, 09:09 AM UTC
Duration
3d 23h
Detected by Pingoru
Mar 12, 2026, 09:33 AM UTC

Affected components

GRA

Update timeline

  1. identified Mar 12, 2026, 09:33 AM UTC

    We are currently investigating an incident affecting our MongoDB Discovery offering in the GRA Region. Here are some supplementary details : Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations are temporarily unavailable. Existing database services continue to run but may be impacted due to degraded self-healing capabilities. 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.

  2. monitoring Mar 13, 2026, 10:08 AM UTC

    MongoDB Discovery offering has been fully restored since 13/03/2026 09:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations were temporarily unavailable. Existing database services continued to run but might have been impacted due to degraded self-healing capabilities. Root cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Mar 16, 2026, 09:09 AM UTC

    We are pleased to inform you that the incident affecting our MongoDB Discovery offering has been resolved. Start time : 10/03/2026 23:40 UTC End time : 13/03/2026 09: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.