Shock Hosting incident

DE-S1 - Service Degradation

Minor Resolved View vendor source →

Shock Hosting experienced a minor incident on November 21, 2025, lasting —. The incident has been resolved; the full update timeline is below.

Started
Nov 21, 2025, 10:30 AM UTC
Resolved
Nov 21, 2025, 10:30 AM UTC
Duration
Detected by Pingoru
Nov 21, 2025, 10:30 AM UTC

Update timeline

  1. resolved Nov 21, 2025, 10:30 AM UTC

    Type: Incident Duration: 6 days, 1 hour and 33 minutes Affected Components: Frankfurt Nov 21, 10:30:31 GMT+0 - Identified - We are currently experiencing an issue on our DE-S1 node due to a system-level resource problem. This has temporarily affected access to cPanel/WHM and, most notably, databases. This appears to have been caused by a spike in filesystem usage. We are working to restore full functionality as soon as possible. Nov 22, 13:19:25 GMT+0 - Identified - Accounts are still being restored. Due to the large amount of accounts and data we expect all accounts to be restored within 24 hours. Nov 21, 19:47:42 GMT+0 - Monitoring - We have detected MySQL corruption on the DE-S1 node, which has impacted access to cPanel/WHM and several databases. To resolve this, we are preparing a careful restoration process from our backups. This involves: 1. Securing all current data to prevent losses. 2. Restoring affected databases and services from verified backups. 3. Validating data integrity and bringing all services back online. This process is complex and will take some time to complete safely. We are actively working on it and will provide regular updates as progress continues. Nov 22, 03:09:08 GMT+0 - Identified - We are still working to resolve this issue as quickly as possible. Due to the large amount of data it is taking an extended amount of time to backup and restore. Nov 23, 06:22:10 GMT+0 - Identified - Restoration progress is currently around 80%. If you wish to know whether your account has been processed yet, please reach out. Nov 23, 20:04:50 GMT+0 - Identified - Thank you for your patience. The majority of the restoration process is now complete. Unfortunately, \~10% of the automated restores were only partially completed. Our team is reviewing and resolving these cases individually, which may take some time. We will provide another update once this is finished. Nov 27, 12:03:57 GMT+0 - Resolved - We are pleased to confirm that the restoration process has now been fully completed. We sincerely apologize for the inconvenience this incident may have caused. Our team has worked diligently to minimize impact and ensure stability moving forward. Thank you for your patience, understanding, and cooperation throughout this period. We truly appreciate your support. If you experience any issues or need assistance, please feel free to contact our support team.