Shock Hosting incident

DE-S1 - Service Degradation

Minor Resolved View vendor source →

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

Started
Nov 21, 2025, 10:30 AM UTC
Resolved
Nov 27, 2025, 12:03 PM UTC
Duration
6d 1h
Detected by Pingoru
Nov 21, 2025, 10:30 AM UTC

Update timeline

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

    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..

  2. monitoring Nov 21, 2025, 07:47 PM UTC

    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. .

  3. identified Nov 22, 2025, 03:09 AM UTC

    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..

  4. identified Nov 22, 2025, 01:19 PM UTC

    Accounts are still being restored. Due to the large amount of accounts and data we expect all accounts to be restored within 24 hours..

  5. identified Nov 23, 2025, 06:22 AM UTC

    Restoration progress is currently around 80%. If you wish to know whether your account has been processed yet, please reach out..

  6. identified Nov 23, 2025, 08:04 PM UTC

    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..

  7. resolved Nov 27, 2025, 12:03 PM UTC

    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..