OVHcloud Web Hosting Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
SharedSQL, CloudDB
Scheduled Maintenance
Report for Web Cloud
Completed
Nous migrons les registry de nos images dockers sur un nouveau serveur.
Pour prendre en compte cette modification, ce changement nécessite le redémarrage du service docker et entraînera une indisponibilité de 5 minutes.
Vous trouverez le planning détaillé dans les commentaires.
Nous commençons cette opération à mardi 28/04/2020 à 14h CET par les clusters sql006, sql007
---
We are migrating our docker registries to a new server.
In order to manage this change, we need to restart the docker service, a 5 minutes downtime is expected.
You’ll find the detailed planning in the following comments.
We will begin this operation on Tuesday 2020-04-28 at 14:00 CET with sql006, sql007 clusters
Update(s):
Date: 2020-05-13 09:06:30 UTC
Intervention completed successfully on sql021
Date: 2020-05-13 08:51:09 UTC
The intervention is starting on sql021.
Date: 2020-05-12 15:18:18 UTC
A downtime is scheduled for tomorrow morning on sql021 to finalize this operation.
We will add a more accurate time tomorrow morning before starting it.
Date: 2020-05-07 14:22:51 UTC
Intervention completed successfully.
Date: 2020-05-07 14:13:46 UTC
The intervention is starting on sql008.
Date: 2020-05-06 13:06:59 UTC
Intervention completed successfully on sql025
Date: 2020-05-06 12:50:25 UTC
Intervention completed successfully on sql024
The intervention is starting on sql025
Date: 2020-05-06 12:44:03 UTC
Intervention completed successfully on sql023
The intervention is starting on sql024
Date: 2020-05-06 12:26:46 UTC
Intervention completed successfully on sql022
The intervention is starting on sql023
Date: 2020-05-06 12:10:41 UTC
Intervention completed successfully on sql021
The intervention is starting on sql022
Date: 2020-05-06 09:22:12 UTC
Intervention completed successfully on sql004
The intervention is starting on sql021
Date: 2020-05-06 08:45:49 UTC
Intervention completed successfully on sql002
The intervention is starting on sql004
Date: 2020-05-06 08:02:51 UTC
The intervention is starting on sql002
Date: 2020-05-05 16:45:42 UTC
Intervention completed successfully on sql020
Date: 2020-05-05 15:07:35 UTC
Intervention completed successfully on sql010
The intervention is starting on sql020
Date: 2020-05-05 14:37:25 UTC
Intervention completed successfully on sql009
The intervention is starting on sql010
Date: 2020-05-05 14:11:15 UTC
The intervention is starting on sql009
Date: 2020-04-30 09:38:42 UTC
Intervention completed successfully
Date: 2020-04-30 08:01:01 UTC
The intervention is starting on sql007
Date: 2020-04-28 14:38:09 UTC
The intervention completed successfully. Depending on the hosts, the unavailability was from 1 to 10 minutes.
Next intervention: sql007 tomorrow.
Date: 2020-04-28 12:11:50 UTC
The intervention is starting…
Pour prendre en compte cette modification, ce changement nécessite le redémarrage du service docker et entraînera une indisponibilité de 5 minutes.
Vous trouverez le planning détaillé dans les commentaires.
Nous commençons cette opération à mardi 28/04/2020 à 14h CET par les clusters sql006, sql007
---
We are migrating our docker registries to a new server.
In order to manage this change, we need to restart the docker service, a 5 minutes downtime is expected.
You’ll find the detailed planning in the following comments.
We will begin this operation on Tuesday 2020-04-28 at 14:00 CET with sql006, sql007 clusters
Update(s):
Date: 2020-05-13 09:06:30 UTC
Intervention completed successfully on sql021
Date: 2020-05-13 08:51:09 UTC
The intervention is starting on sql021.
Date: 2020-05-12 15:18:18 UTC
A downtime is scheduled for tomorrow morning on sql021 to finalize this operation.
We will add a more accurate time tomorrow morning before starting it.
Date: 2020-05-07 14:22:51 UTC
Intervention completed successfully.
Date: 2020-05-07 14:13:46 UTC
The intervention is starting on sql008.
Date: 2020-05-06 13:06:59 UTC
Intervention completed successfully on sql025
Date: 2020-05-06 12:50:25 UTC
Intervention completed successfully on sql024
The intervention is starting on sql025
Date: 2020-05-06 12:44:03 UTC
Intervention completed successfully on sql023
The intervention is starting on sql024
Date: 2020-05-06 12:26:46 UTC
Intervention completed successfully on sql022
The intervention is starting on sql023
Date: 2020-05-06 12:10:41 UTC
Intervention completed successfully on sql021
The intervention is starting on sql022
Date: 2020-05-06 09:22:12 UTC
Intervention completed successfully on sql004
The intervention is starting on sql021
Date: 2020-05-06 08:45:49 UTC
Intervention completed successfully on sql002
The intervention is starting on sql004
Date: 2020-05-06 08:02:51 UTC
The intervention is starting on sql002
Date: 2020-05-05 16:45:42 UTC
Intervention completed successfully on sql020
Date: 2020-05-05 15:07:35 UTC
Intervention completed successfully on sql010
The intervention is starting on sql020
Date: 2020-05-05 14:37:25 UTC
Intervention completed successfully on sql009
The intervention is starting on sql010
Date: 2020-05-05 14:11:15 UTC
The intervention is starting on sql009
Date: 2020-04-30 09:38:42 UTC
Intervention completed successfully
Date: 2020-04-30 08:01:01 UTC
The intervention is starting on sql007
Date: 2020-04-28 14:38:09 UTC
The intervention completed successfully. Depending on the hosts, the unavailability was from 1 to 10 minutes.
Next intervention: sql007 tomorrow.
Date: 2020-04-28 12:11:50 UTC
The intervention is starting…
This scheduled maintenance affected: Web Hosting || Datacenter GRA (Cluster002, Cluster003, Cluster006, Cluster007, Cluster011, Cluster012, Cluster013, Cluster014, Cluster015, Cluster017, Cluster020, Cluster021, Cluster023, Cluster024, Cluster025, Cluster026, Cluster027, Cluster028, Cluster029, Cluster030, Cluster031).