Skip to main content
WP Engine logo

Is WP Engine Down?

No — WP Engine is up

Reachable from all 8 checked regions

Average response time: 780ms

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
731ms
Avg response, 30 days

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

30-day history

76-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 56 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 39 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 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.

iad
220ms
DNS 22ms TCP 1ms TLS 8ms TTFB 201ms
jnb
1618ms
DNS 184ms TCP 1ms TLS 9ms TTFB 1253ms
lax
346ms
DNS 51ms TCP 2ms TLS 18ms TTFB 322ms
lhr
555ms
DNS 0ms TCP 1ms TLS 9ms TTFB 535ms
nrt
1249ms
DNS 318ms TCP 1ms TLS 9ms TTFB 977ms
ord
232ms
DNS 20ms TCP 1ms TLS 8ms TTFB 218ms
sin
1462ms
DNS 85ms TCP 1ms TLS 7ms TTFB 971ms
sjc
565ms
DNS 32ms TCP 1ms TLS 7ms TTFB 415ms

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 up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Kinsta
Kinsta
W
WordPress
Bluehost
Bluehost
Cloudflare
Cloudflare

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 — the most recent check ran from 8 of them.
  • 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 up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required