Hello Hostinger team,

Quick update with a NEW separate issue, in addition to our previous message about the latency window:

Since today, authenticated admin pages (e.g. /admin/branches) intermittently return "500 Server Error" from Laravel, while guest access works fine (302 to login, home page 200 in ~0.4s). The pattern — guests never reach the admin code path, logged-in users get 500 — points to corrupted compiled views / session / cache files, most plausibly leftovers from the saturation era before yesterday's shield fix.

We are running a maintenance routine on the app now: clearing bootstrap/cache, storage/framework/views, storage/framework/cache and storage/framework/sessions (a standard optimize:clear + session purge equivalent). If any 500 persists after that, we will extract the exact exception (timestamp + message + file:line) from storage/logs/laravel.log and share it here.

If your side captured anything for these 500s (PHP-FPM errors, segfaults, OOM kills, disk I/O errors, or inode/quota alerts) for today, please share it — especially disk free space, since the earlier saturation period could have filled the quota and write failures would explain exactly this symptom.

Also, regarding our previous latency thread: the key fix we mentioned was applied via the same maintenance routine (GEMINI_API_KEY restored and verified live against Google's API from the server, config cache cleared). We reiterate the request to re-slice the 24-hour measurement window starting from the last configuration change (the shield install at 05:58:38 UTC, and this maintenance run today), excluding hcdn 403 challenge responses.

Best regards,
