WordPress
WordPress maintenance mode: why a site gets stuck
WordPress uses a temporary maintenance state while updates are being applied. If the update process is interrupted, visitors can keep seeing the maintenance message even though no update is actively running.
First determine whether an update is still running
Do not remove a maintenance marker while a package update or database migration is genuinely active. Check the control panel, deployment process, logs, and recent update activity before treating the state as stale.
A stale maintenance state may be only the visible symptom
The update may have stopped because of a PHP error, file permission problem, full disk, process timeout, or unavailable dependency. Clearing maintenance mode without checking the cause can expose a partially updated site.
Verify plugins, themes, core, and the database after recovery
Confirm the intended versions actually installed, then test the administrator area and important public pages. If a database update was expected, verify WordPress completed it before assuming the site is finished.
Use staging for risky updates
Routine security updates should not require a ceremony, but major plugin, theme, PHP, or ecommerce changes deserve a staging test and a recent restore point. That makes a failed update a rollback problem instead of an outage investigation.