Black FridayCyber Monday 2026
13Days
14Hrs
18Mins
38Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

“Briefly Unavailable for Scheduled Maintenance”: Get WordPress Out of Maintenance Mode

A failed update can leave WordPress showing a maintenance message. Learn how the .maintenance file works, how long it lasts and how to end it safely.

wpallsolution Updated 6 min read

When a WordPress site suddenly shows only “Briefly unavailable for scheduled maintenance. Check back in a minute.”, it is in maintenance mode, almost always because an update started and did not finish cleanly. The site is not necessarily broken. This guide explains how that message is produced, when WordPress ends it on its own, and how to remove it safely when it stays.

Quick answer

During an update, WordPress creates a small file named .maintenance in the main WordPress folder. While that file is recent, visitors get the maintenance message and an HTTP 503 response. WordPress treats the file as expired after 10 minutes, so a leftover file normally stops blocking the site by itself. If the message is still there, check that no update is running, take a backup, delete the .maintenance file, then clear your caches.

How this guide was prepared: it is research-based. We read the WordPress source code and developer reference listed under Sources, checked on October 23, 2026. We did not interrupt an update on a client site to reproduce the problem, so treat the steps as the documented behaviour plus careful practice, not a guarantee for every host.

How maintenance mode works

When WordPress updates core, a plugin or a theme, it writes the .maintenance file, a one line PHP file that stores the time the update began. WordPress deletes the file when the update finishes. If the process is interrupted (a timeout, a closed browser, a crash), the file can stay behind.

  • What visitors see: WordPress ends the request early and shows “Briefly unavailable for scheduled maintenance. Check back in a minute.” with the title “Maintenance”, an HTTP 503 status and a Retry-After header of 600 seconds. Because the request ends early, this applies to the dashboard as well.
  • How long it lasts: in the WordPress code, if the time stored in the file is 10 minutes old or more, maintenance mode is considered over.
  • A custom page: if a file named maintenance.php exists in wp-content, WordPress shows that instead of the default message.

The .maintenance file name starts with a dot, so many file managers hide it. Turn on “show hidden files” to see it.

The decision tree: wait or remove the file?

Flowchart for a WordPress site stuck in maintenance mode: five questions covering the 10 minute wait, update state, backup, the .maintenance file and caches
Five questions show whether to wait or remove the .maintenance file.
  1. Update started less than 10 minutes ago? Wait; WordPress ends the mode itself (Step 1).
  2. No update running now? Check what the update left behind (Step 2).
  3. No recent backup? Make one before you edit files (Step 3).
  4. Message still there after 10 minutes? Remove the .maintenance file (Step 4).
  5. Still seeing the message or an old page? Clear caches and verify (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Message right after you clicked UpdateThe update is still runningStep 1
Message stays for more than 10 minutesA leftover .maintenance file or a cached 503 pageSteps 4 and 5
Message says something different, such as “Coming soon”A maintenance or coming soon plugin, not WordPress coreStep 2
Site loads but the update screen says another update is runningThe update lock is still activeSee the lock guide below

5 steps to get WordPress out of maintenance mode

Step 1: Wait 10 minutes

Do not start another update. WordPress itself stops treating the file as active once it is 10 minutes old, so waiting is often enough. Note the clock time and try the site again after 10 minutes.

Step 2: Check what the update left behind

Find out which update ran: core, a plugin or a theme. Open your hosting file manager or SFTP, turn on hidden files and look in the WordPress folder for .maintenance. Also look inside wp-content for an upgrade folder with leftover files. If the message does not match WordPress’s wording, you may be using a maintenance plugin, which you would switch off from its own settings instead. If you also see “Another update is currently in progress”, read our guide to the update lock.

Step 3: Take a backup

Back up the files and the database before you delete or change anything, and be sure you can restore them. See is your WordPress backup really safe.

Step 4: Delete the .maintenance file

If the message remains after 10 minutes and no update is running, delete the .maintenance file from the main WordPress folder (the same place as wp-config.php). Make sure you remove only that file. Reload the site in a private window.

Step 5: Clear caches and verify

A page cache, a server cache or a CDN may have stored the 503 page. Clear your caching plugin, your host’s cache and your CDN, then test again. Finally, go back to Dashboard → Updates and finish the update that was interrupted. Plugins and themes that were halfway updated may need to be updated again, and our guide to finding the plugin that broke your site helps if something now misbehaves.

Version and hosting differences

  • The 10 minute rule and the 503 behaviour come from the current WordPress source. Very old versions may differ.
  • If your host updates WordPress for you, a leftover file may come from their tool, so tell them before you delete anything.
  • Some hosts block file edits from the dashboard, so you may need SFTP or the host’s file manager.

How to verify the fix

  • The home page and the admin login open normally in a private window.
  • No .maintenance file is left in the WordPress folder.
  • Dashboard → Updates shows no unfinished update, and Site Health has no new critical issue.
  • Forms, logins and, on a store, a test checkout still work.

How to prevent it from happening again

Frequently asked questions

Does this message mean my site was hacked?

No. It is the normal WordPress maintenance message. A failed or interrupted update is the usual reason.

Why can I not log in either?

WordPress ends the request early in maintenance mode, so the dashboard shows the same message until the mode ends.

Will it fix itself?

Usually yes, after about 10 minutes, because WordPress ignores an older .maintenance file. A cached page can still make it look stuck.

Is it safe to delete the file?

Yes when no update is running and you have a backup. It only signals that an update is happening, and WordPress recreates it during the next update.

What to do next

Wait 10 minutes, check the update state, back up, then remove the file and clear your caches. If the site is still down or the update left things broken, wpallsolution offers an emergency WordPress fix and WordPress maintenance packages. We cannot promise a result without seeing your setup.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us