A healthy single WordPress plugin update takes 10-60 seconds, with large plugins taking longer. Start worrying if maintenance mode lasts beyond 1-2 minutes, and treat any single update still running after about 10 minutes as stalled. A plugin update replaces old plugin files with a newer version. WordPress shows visitors a "Briefly unavailable for scheduled maintenance" message during that swap, then returns the site to normal.
Table of Contents
- What does a normal update look like?
- How do you know it is stuck?
- Why do updates stall?
- What should you do safely?
What does a normal update look like?
A simple plugin often finishes in seconds. SiteHale reports that healthy single updates normally complete in 10-60 seconds each, with bulk updates averaging about one minute per plugin on shared hosting in SiteHale's update timing guide. Core updates and large tools need more time.
Page builders and WooCommerce are common slow cases because they ship more files. Maintenance mode should disappear fast. ToolXray notes that normal maintenance lasts only seconds to about a minute, so a persistent message beyond 1-2 minutes signals trouble in ToolXray's maintenance-mode guide.
How do you know it is stuck?
Watch the clock, not the spinner. A simple plugin may show maintenance for roughly 3-5 seconds, while core may take 10-30 seconds. If the message remains after 1-2 minutes, the update likely did not finish cleanly.
Do not keep waiting indefinitely. Any single plugin update still running after about 10 minutes is probably stalled rather than slow. That is the point to investigate instead of giving it more time.
Why do updates stall?
WordPress creates a hidden `.maintenance` file before updating and deletes it afterward. An interrupted update leaves that file behind, so visitors stay locked on the maintenance message until someone deletes it through FTP or File Manager. Server limits can interrupt the file replacement.
PHP's `max_execution_time` defaults to 30 seconds, according to the PHP configuration manual, so a slow or large update can stop mid-extraction and leave incomplete files. WordPress also checks the `$upgrading` timestamp and automatically ignores a `.maintenance` file older than about 10 minutes. A site still locked after that point points to a deeper failure, timeout, or conflict.
What should you do safely?
Make a complete backup before updating so a failed update can be restored. Official WordPress upgrade documentation gives that backup step as the required preparation for one-click updates.
Then update one plugin at a time without closing the browser until "Completed" appears. This makes it easier to see which plugin caused the problem.
- Update one plugin, wait for completion, then continue.
- Keep the update tab open during the process.
- Check the front end after each update.
- Do not confuse slow installation with WordPress.org's 6-24-hour new-release holding period since June 2026, which delays when auto-updates appear.
