July 2026

The I/O operations freeze is over. I/O operations were suspended from 20:09 to 20:25. Our maintenance operation is still in progress, but no further impact on the VPS is expected.

Our maintenance operation is about to begin. As a reminder, I/O operations will be suspended on the VPS affected by the maintenance operation, for an estimated maximum duration of 20 minutes.

Maintenance is now in progress

We would like to inform you that an emergency maintenance operation is planned on one of our SATA storage units, used by our PAR02 and PAR06 clusters, at our Paris POP. During this operation, I/O operations will be interrupted on the affected VPS.

Date: Saturday 25 July 2026, between 20:00 and 22:00.

This operation is part of an emergency maintenance, made necessary by a hardware component failure on the storage unit concerned, which unfortunately cannot be replaced hot.

The affected VPS will not be shut down during this maintenance, however I/O operations (read and write) will be suspended for an estimated duration of 20 minutes, within the scheduled time window. This maintenance will only affect a small portion of the VPS hosted on the "PAR06" and "PAR02" clusters (only VPS with a SATA storage disk will be affected, such as the "VPS STOR" plans, or the "Classic Cloud" plans that have subscribed to the additional SATA disk option).

In the vast majority of cases, no action is required on your part, however we invite you to:

• Check the status of your backups (we nevertheless emphasize that no data loss is expected);

We thank you for your understanding.

The incident is now resolved

On 22 July 2026, between 21:31 and 21:52, a temporary malfunction affected a virtualization node of the PAR06 cluster. The VPS hosted on this node may have experienced slowdowns during this period.

Our teams intervened immediately and the situation returned to normal at 21:52. The node has been stable since then and all services are operating normally.

We apologize for the inconvenience caused.

After a full check of all hosted sites, we confirm that everything is back to normal. All services are operating correctly.

This incident followed an automatic update of certain PHP versions and the integration of an exception by CloudLinux. During a routine reload of the PHP-FPM services in the morning, several versions ended up listening on the same port, which prevented some of them, particularly the older ones, from starting. This is why only some sites were affected.

Resolving it proved especially delicate: the fix had to work in tandem with Plesk, which required careful work to restore access without affecting the rest of the platform. Our teams put a reliable workaround in place, pending the definitive fix released by the vendor.

We apologize for the inconvenience and thank you for your patience throughout its resolution.

We have identified a bug introduced by CloudLinux in certain PHP versions, which explains why the issue only affected some sites. A first fix was deployed at around 09:10\. We are no longer seeing any errors at this stage. Our teams are continuing a detailed check of all hosted sites to make sure nothing is overlooked.

We are currently experiencing an incident affecting access to some websites hosted on our FRWEB14 server. Our technical teams are fully mobilized and are actively working to restore service as quickly as possible.

The maintenance operation is complete, all affected VPS have been restarted, with an average downtime of 8 minutes.

Our maintenance operation is about to begin. As a reminder, VPS located on the MRS05 cluster will be shut down for a maximum estimated duration of 15 minutes, then restarted, during this maintenance operation.

Maintenance is now in progress

We would like to inform you that routine maintenance is scheduled for the MRS05 cluster of our Classic Cloud VPS range this Friday, July 17, 2026. During this operation, the VPS hosted on this cluster will be restarted.

Date: Friday, July 17, 2026, between 9:00 PM and 11:00 PM.

This operation is part of our routine maintenance, aimed at keeping our infrastructure operational.

The affected VPS will be powered off for a maximum of 15 minutes during the scheduled time slot, and then restarted. Only VPSs from our "Classic Cloud" range hosted on the "MRS05" cluster will be affected during this operation. You can check the cluster where your VPS is located directly from your customer area, on the relevant VPS's information page.

In the vast majority of cases, no action is required on your part, but we nevertheless encourage you to:

• Verify that your applications installed on the VPS are correctly configured to function after a restart;

• Check the status of your backups (we emphasize that no data loss is expected; the VPS will simply be powered off and then restarted);

• Whenever possible, properly suspend your activity before 9:00 PM, especially if you host applications sensitive to restarts (databases, etc.).

Thank you for your understanding.

The maintenance operation is complete. All affected VPS have been restarted, with an average downtime of 11 minutes.

Our maintenance operation is about to begin. As a reminder, VPS located on the PAR06 cluster will be shut down for an estimated maximum duration of 15 minutes, then restarted, during this maintenance operation.

Maintenance is now in progress

We would like to inform you that routine maintenance is scheduled for the PAR06 cluster of our VPS Classic Cloud range this Wednesday, July 16, 2026\. During this operation, the VPS hosted on this cluster will be restarted.

Date: Wednesday, July 16, 2026, between 9:00 p.m. and 11:00 p.m.

This operation is part of our routine maintenance operations, with the aim of keeping our infrastructure in operational condition.

The affected VPS will be powered off for a maximum of 15 minutes during the scheduled time slot, then restarted. Only VPSs from our "Classic Cloud" range hosted on the "PAR06" cluster will be affected by this operation. You can check the cluster where your VPS is located directly from your customer area, on the VPS's information page.

In the vast majority of cases, no action is required on your part, but we nevertheless encourage you to:

• Verify that your applications installed on the VPS are correctly configured to work after a reboot;
• Check the status of your backups (we nevertheless insist that no data loss is expected, the VPS will simply be turned off, then restarted);
• Where possible, properly suspend your activity before 9:00 PM, especially if you host applications sensitive to restarts (databases, etc.).

Thank you for your understanding.