Option 1: Do it yourself
Follow the steps in this guide. Free, and typically 30 minutes to a few hours of careful work.
Option 2: Just contact us
Skip every step below. $49/mo and it is sorted, or WhatsApp us right now.
Last updated: August 2026
Why this happens
Every time WordPress updates core, a plugin or a theme, it drops a .maintenance file in the root directory so visitors see the friendly notice instead of a half-updated site. If the update is interrupted, a timeout, a lost connection, closing the browser tab mid-update, or updating too many plugins at once, the process dies before cleanup and the file stays. The site is fine; the sign on the door just never came down.
The fix, step by step
- Open your hosting control panel and launch the file manager (or connect via SFTP).
- Navigate to your website's root folder, the one containing wp-config.php and the wp-admin folder.
- Enable "show hidden files" in the file manager settings, because names starting with a dot are hidden by default.
- Find the file named exactly .maintenance and delete it.
- Reload your website. It is back instantly.
No restart, no restore, no waiting. This is genuinely a two-minute repair.
One more check before you leave
The interrupted update that stranded the file may itself be incomplete. Log into wp-admin, open Dashboard, Updates, and see whether the plugin or core update that was running shows as pending or failed. Re-run it properly, one item at a time, with a backup first. If the same update keeps failing, the timeout has a cause worth finding: a slow server, a huge plugin package, or a PHP execution limit set too low.
Preventing the repeat
Three habits end this forever: update plugins in small batches instead of clicking Update All on nineteen items, never close the tab while updates run, and keep hosting responsive enough that updates do not time out. Sites on overloaded shared servers hit this loop repeatedly because slow servers time out mid-update; it is one of the small, telling symptoms of outgrown hosting.
If updates and their occasional weirdness are exactly the chores you would rather never think about, that is literally the job description of a maintenance plan: we run every update in a safe sequence with snapshots, and stuck maintenance mode becomes a thing you once read about.
FAQ
I deleted .maintenance but the notice still shows. Why? Caching. Clear your caching plugin, your host's server cache and your CDN, then test in an incognito window. The file was the cause; the cache is the echo.
There is no .maintenance file in my root folder. What now? Confirm hidden files are visible first. If it is truly absent, a maintenance-mode or coming-soon plugin is likely enabled; check your plugins list, or rename the suspect plugin's folder to deactivate it.
Is my data at risk while stuck in maintenance mode? No. Nothing is broken or lost; the site is simply displaying a static notice. Your content, orders and settings are untouched.
Can I prevent WordPress from using maintenance mode at all? You can, but should not: updating live files while visitors browse causes real errors. The mode is good; only the stranding is bad.
You do not have to do any of this yourself
Skip the steps above. Our engineers handle security, updates, speed, backups and fixes for you, with a 12-minute average response and a 99.99% uptime target.