We would like to inform you that the incident on RBX3 has now been resolved.
Here is detail for this incident :
Start time : 17/04/2025 04:55 UTC End time : 17/04/2025 05:12 UTC
We thank you for your understanding and patience throughout this incident.
Posted Apr 17, 2025 - 05:15 UTC
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Most of servers are operational again. 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.
Posted Apr 17, 2025 - 05:01 UTC
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : A significant number of servers are operational again. 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.
Posted Apr 17, 2025 - 04:54 UTC
Identified
We have determined the origin of the incident affecting our Dedicated Servers offer on the specific rack.
Here are some supplementary details : Start time : 17/04/2025 04:55 UTC Impacted Service(s) : Servers in rack 45F17 are temporarily unreachable. Customers Impact : Customers are temporarily unable to access their servers through public network. Root Cause : This incident is caused by a network equipment issue. Ongoing Actions : The incident has been identified and our teams are mobilized 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.
Posted Apr 17, 2025 - 04:20 UTC
This incident affected: Dedicated Servers || Network (RBX).