Service not responding

Update timeline

1. investigating Apr 29, 2026, 07:02 AM UTC

   We are currently experiencing a problem with the services not responding. We are working on this issue and will post an update as soon as possible.

2. identified Apr 29, 2026, 07:36 AM UTC

   We have identified the issue, related to an electrical fault, and are working on a solution.

3. identified Apr 29, 2026, 09:07 AM UTC

   We have identified that the disruption is related to an electrical fault in our local infrastructure. The fault is affecting the voltage, causing parts of our equipment to shut down as a protective measure to prevent hardware damage. It also affects our ability to redirect traffic to an alternative hosting environment as intended. Our technicians are working together with electricians to resolve the issue as soon as possible. We will also address the dependency that caused our redundancy to be affected in this situation. We apologize for the disruption and will provide another update as soon as we have more information.

4. monitoring Apr 29, 2026, 11:01 AM UTC

   A solution is now in place for the issue caused by the electrical fault in our local infrastructure, and affected services are operating normally again. We are continuing to monitor the situation closely and sincerely apologize for the disruption. In parallel, we are putting even greater focus on our ongoing work to remove dependencies between our hosting sites. This work began after the incident in early January, and several important changes have already been made. We will continue this effort to strengthen our redundancy and reduce the risk of similar situations affecting failover in the future.

5. resolved May 02, 2026, 08:20 AM UTC

   Resolved - We are now closing this incident and returning to normal operations. Since the issue occurred on Wednesday, we have actively monitored our systems and followed up on related effects from the incident. After the restart, some services experienced limited availability due to parts of the server environment not being fully visible, which may have affected some users. These issues have been addressed as they were identified. The incident was caused by an electrical fault in our local infrastructure. We will continue our ongoing work to further separate dependencies between our hosting sites and strengthen our redundancy. We sincerely apologize for the disruption and thank you for your patience.