Resolved -
We are pleased to inform you that the incident affecting our Dedicated Servers has been resolved.
All servers in racks T05B25/T05B26/T05B27 are now fully operational.
Start time : 19/03/2026 16:46 UTC
End time : 20/03/2026 04:04 UTC
Root Cause : This incident was caused by a cooling system issue.
We apologize for any inconvenience caused and appreciate your understanding.
Mar 20, 04:06 UTC
Update -
Please find below an update on the situation:
Impacted Service(s) : All servers in rack T05B27 are fully operational.
Some servers in racks T05B25/T05B26 are still temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located in racks T05B25/T05B26.
Root Cause : This incident is caused by a cooling system issue.
Ongoing Actions : 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.
Mar 20, 00:30 UTC
Update -
Please find below an update on the situation:
Impacted Service(s) : Some servers in the racks T05B25/T05B26/T05B27 are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located on the specified racks.
Root Cause : This incident is caused by a cooling system issue.
Ongoing Actions : 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.
Mar 19, 21:05 UTC
Update -
Please find below an update on the situation:
Update : Servers are still unavailable for the following racks :
T05B25
T05B26
T05B27
The public network is operational for the following racks :
T05B38
Root Cause : This incident is caused by a network equipment issue.
Ongoing Actions : 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.
Mar 19, 17:42 UTC
Update -
Please find below an update on the situation:
Update : Servers are still unavailable, mostly in the following racks:
T05B25
T05B26
T05B27
T05B38
The public network is operational for the following racks :
T05B34
T05B35
T05B37
T05B39
The Private network (vRack) is operational for the following racks :
T04E29
T04E30
T05B31
T05B32
T05B33
T05B34
T05B35
T05B38
T05B39
T05C22
T05E30
Ongoing Actions : 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.
Mar 19, 17:29 UTC
Identified -
We have determined the origin of the incident affecting our Dedicated Servers offering on the room T5B.
Here is detail for this incident :
Start time : 19/03/2026 16:46 UTC
Impacted Service(s) : Some servers in the room T05B are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located on the specified room.
Root Cause : This incident is caused by a network equipment issue.
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.
Mar 19, 17:11 UTC
Update -
We are continuing to investigate this issue.
Mar 19, 16:59 UTC
Investigating -
We are currently investigating an incident affecting our Dedicated Servers offering, which is causing temporary availability issue in the room T05B.
Here are some supplementary details :
Start time : 19/03/2026 16:46 UTC
Impacted Service(s) : Some servers in the room T05B are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located on the specified room.
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.
Mar 19, 16:56 UTC