Skip to main content

Is WP Engine Down?

No — WP Engine is up

Reachable from all 8 checked regions

Average response time: 657ms

Last checked · checks run every 6 hours

Official status page: https://wpenginestatus.com

WP Engine uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
666ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 25 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

25-day clean streak
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: 100.00% uptime, 16 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 32 checks
Aug 3: 100.00% uptime, 30 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 38 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 31 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 30 checks
Aug 19: 100.00% uptime, 40 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 41 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Jul 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
1033ms
DNS 0ms TCP 2ms TLS 8ms TTFB 940ms
arn
765ms
DNS 0ms TCP 2ms TLS 22ms TTFB 538ms
lhr
804ms
DNS 0ms TCP 3ms TLS 9ms TTFB 627ms
nrt
514ms
DNS 0ms TCP 1ms TLS 8ms TTFB 338ms
ord
243ms
DNS 0ms TCP 2ms TLS 7ms TTFB 176ms
sin
423ms
DNS 0ms TCP 1ms TLS 7ms TTFB 406ms
sjc
255ms
DNS 0ms TCP 2ms TLS 10ms TTFB 226ms
syd
1615ms
DNS 0ms TCP 1ms TLS 7ms TTFB 1391ms
yyz
415ms
DNS 0ms TCP 2ms TLS 6ms TTFB 391ms

What WP Engine does

WP Engine is a managed WordPress host used by agencies and businesses that would rather not run servers themselves, bundling hosting, caching, staging environments and a CDN. Customer sites sit on its platform behind its own edge, so an incident can take out the public site and the portal used to diagnose and fix it at the same time.

What an outage looks like

Sites return 502 or 504 errors, or keep serving a cached homepage while every other page fails. WordPress admin logins redirect in a loop or land somewhere unexpected, and custom page URLs return 404 while the same content still resolves at its default permalink. The User Portal can become unreachable, so cache flushes, deploys and backup restores cannot be triggered.

What to do about it

Check wpenginestatus.com, which lists active incidents with a count of affected environments alongside a maintenance calendar, so planned work is distinguishable from a fault. Resist reinstalling plugins or rewriting permalinks to chase symptoms that match a posted platform incident, because those changes are harder to unpick afterwards. With nothing posted, open support from the User Portal.

Is it down for everyone, or just you?

If this page says WP Engine is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

WP Engine outage FAQ

Is WP Engine down or is it just my site?
Load wpengine.com itself and then a site you host elsewhere. A WP Engine site failing while the company's own site and the rest of your browsing work points at the platform or your specific environment rather than your connection. The status page reports how many environments an incident affects, which tells you whether you are inside a known problem or on your own.
Why does my site load but WP Admin redirect in a loop?
Login redirect loops and 404s on custom URLs are a recognised class of WP Engine incident, distinct from the site being unreachable, and they are usually caused at the platform layer rather than by your WordPress install. Check the status page before touching permalink settings or your login plugin, because reconfiguring those to work around a platform fault leaves you with a broken configuration once it is fixed.
Do I lose content or form submissions during an outage?
Content already saved in the database is not lost by an outage. Form submissions attempted while the site is erroring generally never reach the database at all, so they are gone without a trace rather than delayed, and the visitor may believe they succeeded. Check submission counts against a normal day afterwards instead of assuming everything arrived.
Does the CDN keep my site up if the origin fails?
Partly, and unpredictably. Cached pages can keep serving to visitors while the origin is failing, which is why a site sometimes shows a working homepage and errors everywhere else. Anything uncached, logged in, or generated per request goes straight to the origin and fails. The effect is a site that looks half alive rather than cleanly down.
Is scheduled maintenance the same as an outage?
No, and the status page separates them. Maintenance windows are published in advance on a calendar and are usually non-disruptive or briefly disruptive by design. An incident is unplanned and carries a count of affected environments. If your problem coincides with a posted maintenance window, waiting it out is normally the right response.

How we measure this

  • We request WP Engine's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where WP Engine publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when WP Engine goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required