Skip to content
OutageDeck

Incident detail

[GLOBAL][Databases] - Database incident notification

Resolved incidentMajor

Timeline window

to

Outage alerts

Get alerted the next time OVHcloud breaks

Free email alerts for up to 5 providers — no card, live in about a minute. Paid plans add Slack, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow OVHcloud alerts work

Timeline

Incident updates

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

  1. Identified

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offering

    Here are some supplementary details :

    <b>Start time :</b> 19/07/2026 18:00 UTC

    <b>Impacted Service(s) :</b> Some Database are temporarily unavailable.

    <b>Customers Impact :</b> Customers are temporarily unable to access their Database located on the specified region.

    <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.

  2. Identified

    We have new information regarding the incident that affected your service(s).

    Please find below an update on the situation:

    <b>Update : </b> Customers are temporarily unable to access and fork their databases.

    Please note that no data has been lost, and all data remains intact.

    <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. Identified

    Please find an update of this incident below :

    <b>Update:</b> Database access is being progressively restored in all regions, with the exception of GRA11.

    Pending orders are now being progressively delivered. As a precaution, new orders remain temporarily suspended.

    <b>Ongoing Actions :</b> Our teams continue to restore the remaining impacted region and are closely monitoring the situation.

    We will keep you updated on the progress and resolution.

    We apologize for any inconvenience caused and appreciate your understanding.

  4. Monitoring

    <b>Update:</b> Database access has been restored across all regions. Our teams are continuing to work on the remaining impacted databases in GRA11.

    Pending orders are being delivered, and new orders are no longer suspended.

    Monitoring remains in place to ensure long-term stability.

    We apologize for any inconvenience caused and appreciate your understanding and patience.

  5. Resolved

    We are pleased to inform you that the incident affecting our Databases offering has been resolved.

    <b>Start time :</b> 19/07/2026 18:00 UTC

    <b>End time :</b> 21/07/2026 08: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.