Public Cloud Outage History

Public Cloud is up right now

Public Cloud had 84 outages in the last 2 years totaling 6454h 45m of downtime — averaging 3.5 incidents per month.

There were 84 Public Cloud outages since October 30, 2025 totaling 6454h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://public-cloud.status-ovhcloud.com

Major March 12, 2026

[GRA][Databases] - MongoDB Discovery incident notification

Detected by Pingoru
Mar 12, 2026, 09:33 AM UTC
Resolved
Mar 16, 2026, 09:09 AM UTC
Duration
3d 23h
Affected: GRA
Timeline · 3 updates
  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.

Read the full incident report →

Major March 10, 2026

[GRA/DE/SBG/UK/BHS/WAW][Databases] - MongoDB incident notification

Detected by Pingoru
Mar 10, 2026, 08:44 PM UTC
Resolved
Mar 11, 2026, 12:01 AM UTC
Duration
3h 16m
Affected: BHSDEGRASBGUKWAW
Timeline · 3 updates
  1. investigating Mar 10, 2026, 08:44 PM UTC

    We are currently investigating an incident affecting our MongoDB offering in the DE and GRA Region. Here are some supplementary details : Start time : 10/03/2026 16:40 UTC Impacted Service(s) : Management operations are temporarily unavailable (e.g., adding users, updating flavors). Existing database services remain operational and continue to serve customer workloads. 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.

  2. identified Mar 10, 2026, 09:31 PM UTC

    We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our MongoDB offer on the specific GRA - DE - SBG - UK - BHS and WAW regions. Here are some supplementary details : Start time : 10/03/2026 16:40 UTC Impacted Service(s) : Management operations are temporarily unavailable (e.g., adding users, updating flavors). Existing database services remain operational and continue to serve customer workloads. Customers Impact : 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.

  3. resolved Mar 11, 2026, 12:01 AM UTC

    We are pleased to inform you that the incident affecting our MongoDB offering has been resolved. Start time : 10/03/2026 16:40 UTC End time : 10/03/2026 23:40 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →

Major March 10, 2026

[GRA2][Storage] - CEPH incident notification

Detected by Pingoru
Mar 10, 2026, 04:52 PM UTC
Resolved
Mar 10, 2026, 05:46 PM UTC
Duration
54m
Affected: GRA2
Timeline · 3 updates
  1. investigating Mar 10, 2026, 04:52 PM UTC

    We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA2. Here are some supplementary details : Start time : 10/03/2026 07:26 UTC Impacted Service(s) : Some CEPH volumes are not available in this region. Customers Impact : Customers may experience performance degradation and deterioration in their data redundancy. 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.

  2. identified Mar 10, 2026, 04:57 PM UTC

    We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams have replaced the faulty network equipment. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  3. resolved Mar 10, 2026, 05:46 PM UTC

    We would like to inform you that the incident on our Storage Volume Snapshot (Ceph) offer has now been resolved. Here is detail for this incident : Start time : 10/03/2026 07:26 UTC End time : 10/03/2026 17:33 UTC Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

Read the full incident report →

Major March 4, 2026

[GLOBAL][AI & Machine Learning] - LLama3.3-70B model incident notification

Detected by Pingoru
Mar 04, 2026, 02:16 PM UTC
Resolved
Mar 11, 2026, 12:56 PM UTC
Duration
6d 22h
Affected: AI & Machine Learning || AI Endpoint
Timeline · 5 updates
  1. investigating Mar 04, 2026, 02:16 PM UTC

    We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary latency issue in the LLama3.3-70B model. Here are some supplementary details : Start time : 04/03/2026 10:00 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. Customers Impact : Latency and unavailability can be observed on the customer side. 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.

  2. identified Mar 06, 2026, 09:59 AM UTC

    We have new informations regarding the incident that affected your service(s). Please find below an update on the situation: Update : The issue has been identified and is related to an unusually high load on the LLama3.3-70B model. Our teams are monitoring the situation and working to mitigate the impact. 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.

  3. monitoring Mar 06, 2026, 03:23 PM UTC

    Service has been fully restored since 06/03/2026 10:00 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 06/03/2026 15:22 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. We apologize for any inconvenience caused and appreciate your understanding.

  4. identified Mar 09, 2026, 10:26 AM UTC

    We have new information regarding the incident that affected your service(s). Please find below the latest update on the situation: Update : Latency is still being observed on the LLama3.3-70B model. Our teams are actively monitoring the situation to ensure long-term stability. Ongoing Actions : The root cause of the incident has been identified, and our teams remain fully mobilised to restore normal service as quickly as possible. We will continue to keep you informed about the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

  5. resolved Mar 11, 2026, 12:56 PM UTC

    We are pleased to inform you that the incident affecting our AI & Machine Learning offer has been resolved. Start time : 04/03/2026 10:00 UTC End time : 11/03/2026 07:00 UTC Root Cause : This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

Read the full incident report →