'Briefly unavailable for scheduled maintenance': what it means and how to fix it
Quick answer
The 'briefly unavailable for scheduled maintenance' message is not a real maintenance mode. It is WordPress telling you that an update started, dropped a hidden file called .maintenance in the site root, and never finished. Delete that .maintenance file over FTP or the host file manager and the site comes back instantly. If the site goes into the error again on the next update, the update itself is failing because of a plugin conflict or permissions problem, not because maintenance mode is stuck.
What the error actually is
When WordPress starts an update, it writes a tiny file called .maintenance in the site root. That file tells WordPress to show the friendly maintenance message to every visitor.
When the update finishes cleanly, WordPress deletes .maintenance. The site is back in seconds.
If the update crashes, times out, or is interrupted (a plugin update killed by a memory limit, a browser tab closed during upgrade, a plugin fatal error mid update) the .maintenance file is never deleted. The site is stuck showing the message to everyone.
The 60 second fix
- Log in over FTP, SFTP, or your host's file manager. Turn on 'show hidden files', because the filename starts with a dot.
- Delete the .maintenance file from the site root. The site is live again on the next page load.
- Then go to wp-admin and check whether the update that crashed finished. Update any plugin still listed as 'update available' one at a time.
Why it keeps coming back
PHP memory limit too low. Large plugin updates run out of memory and die mid update. Raise memory_limit in wp-config.php to 256M or ask the host to raise it.
A plugin has a fatal error on activation. Every subsequent update trips it and leaves .maintenance behind. Update plugins one at a time to find the offender.
File permissions blocked WordPress from deleting .maintenance itself. The wp-content folder should be 755 with files at 644, owned by the web user.
Prevent it going forward
Run updates from a staging copy first, not on the live site. Every serious host offers one click staging.
Take a fresh backup before any batch update. If an update crashes mid run, you have a clean rollback rather than a stuck site.
For fleets and store sites, use managed updates with staged rollout and monitoring so a crashed update never leaves the customer facing site in maintenance mode.
Common questions
Is 'briefly unavailable for scheduled maintenance' a real maintenance mode?+
No. It is a stuck update. WordPress meant to remove the message when the update finished, but the update never finished. Delete the .maintenance file in the site root and the site is back.
Where is the .maintenance file?+
In the WordPress site root, at the same level as wp-config.php. It is hidden by default. Enable 'show hidden files' in FTP or your host file manager to see it.
How do I stop this happening again?+
Raise the PHP memory limit to at least 256M, run updates from a staging environment, and take a fresh backup before any batch update.
Want this handled for you?
Book a call and we will review your site before recommending anything.