Wordfence Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Wordfence Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Temporarily Unavailable | 352h 45m | Resolved |
| Aug 26, 2026 | Intermittent Performance Issues | 1601h 6m | Resolved |
| Jul 24, 2026 | Investigating Outage | 1644h 46m | Resolved |
| Jun 9, 2026 | Investigating Outage | 2008h 39m | Resolved |
| Jun 9, 2026 | Investigating Outage | 2009h 4m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Wordfence incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Wordfence Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Wordfence acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Wordfence outage in this window ran 83d 17h, against a mean recovery of 63d 11h. If you depend on Wordfence in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.