OVHcloud Web Hosting Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
SharedSQL, Gravelines
Scheduled Maintenance Report for Web Cloud
Completed
To upgrade our systems (security enhancements), we need to reboot our SharedSQL servers, on the Gravelines datacentre. A 2 to 10 minutes downtime is expected per server. You will find the schedule of the interventions on the below comments.

---

Pour mettre à jour nos systèmes (améliorations de sécurité), nous devons redémarrer les serveurs SharedSQL, sur le centre de données de Gravelines. Une coupure de 2 à 10 minutes est à prévoir par serveur. Vous trouverez le planning des interventions dans les commentaires ci-dessous.

Update(s):

Date: 2019-08-08 00:26:47 UTC
Intervention completed on sql025. 30 servers rebooted smoothly.
All the platforms are up-to-date.

Date: 2019-08-07 23:59:03 UTC
Intervention completed on sql024. 32 servers rebooted smoothly.
The intervention is starting on sql025...

Date: 2019-08-07 23:36:15 UTC
Intervention completed on sql023. 34 servers rebooted smoothly.
The intervention is starting on sql024...

Date: 2019-08-07 23:09:40 UTC
The intervention is starting on sql023...

Date: 2019-08-07 01:00:18 UTC
Intervention completed on sql022. 50 servers rebooted smoothly.

Date: 2019-08-07 00:34:55 UTC
Intervention completed on sql006. 48 servers rebooted smoothly.
The intervention is starting on sql022...

Date: 2019-08-06 23:56:40 UTC
Intervention completed on sql006. 46 servers rebooted smoothly.
The intervention is starting on sql021...

Date: 2019-08-06 23:26:48 UTC
The intervention is starting on sql006...

Date: 2019-08-06 01:13:51 UTC
Intervention completed. 35 hosts rebooted smoothly.
sql006 hosts will be postponed for tomorrow.

Date: 2019-08-06 00:21:04 UTC
The intervention is starting on sql004...

Date: 2019-08-02 17:58:30 UTC
Schedule:
2019-08-05, from 00:00 to 04:30 CEST: Gravelines, sql004 and sql006
2019-08-06, from 00:00 to 04:30 CEST: Gravelines, sql021 and sql022
2019-08-07, from 00:00 to 04:30 CEST: Gravelines, sql023, sql024 and sql025

Date: 2019-08-02 00:32:00 UTC
Intervention completed.

Date: 2019-08-02 00:09:33 UTC
db0[01-25].sql002 rebooted successfully. Rebooting db0[26-43].sql002...

Date: 2019-08-01 23:24:31 UTC
The intervention is starting on sql002...

Date: 2019-08-01 00:49:00 UTC
db0[51-61].sql001 rebooted successfully.

Date: 2019-08-01 00:32:06 UTC
db0[41-47,49-50].sql001 rebooted successfully. Rebooting db0[51-61].sql001...

Date: 2019-07-31 23:51:51 UTC
db0[31-40].sql001 rebooted successfully. Rebooting db0[41-47,49-50].sql001...

Date: 2019-07-31 23:32:22 UTC
db0[21-30].sql001 rebooted successfully. Rebooting db0[31-40].sql001...

Date: 2019-07-31 22:57:28 UTC
db0[11-20].sql001 rebooted successfully. Rebooting db0[21-30].sql001...

Date: 2019-07-31 22:37:23 UTC
db0[01-10].sql001 rebooted successfully. Rebooting db0[11-20].sql001...

Date: 2019-07-31 22:10:28 UTC
The intervention is starting on sql001...

Date: 2019-07-29 22:50:19 UTC
sharedsql047.sql020 UP and ready. A part of the filesystem (NOT the customer data) were corrupted. This had been fixed.

Date: 2019-07-29 22:32:04 UTC
We're still investigating on sharedsql047.sql020. Our infrastructure on-call is there to help too.

Date: 2019-07-29 21:44:32 UTC
All reboots went fine. sharedsql047.sql020 is still booting…

Date: 2019-07-29 21:02:21 UTC
The intervention is starting on sql020…

Date: 2019-07-23 13:04:29 UTC
Schedule:
2019-07-29, from 23:00 to 23:30 CEST: Gravelines, sql020
2019-07-31, from 00:00 to 04:00 CEST: Gravelines, sql001
2019-08-01, from 00:00 to 04:00 CEST: Gravelines, sql002, sql006 (part 1/2)
2019-08-02, from 00:00 to 04:00 CEST: Gravelines, sql004, sql006 (part 2/2)
Posted Jul 23, 2019 - 12:53 UTC
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).