MainWP Outage History

10 incidents recorded over the last 365 days, 10 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 MainWP Incident

MainWP incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026mainwp.dev is down350h 38mResolved
Oct 6, 2026community.mainwp.com is down705h 10mResolved
Sep 29, 2026voice.mainwp.com is down878h 35mResolved
Sep 6, 2026voice.mainwp.com is down1439h 59mResolved
Aug 23, 2026voice.mainwp.com is down1662h 14mResolved
Aug 22, 2026voice.mainwp.com is down1680h 59mResolved
Jul 28, 2026voice.mainwp.com is down1552h 0mResolved
Jun 11, 2026voice.mainwp.com is down1962h 53mResolved
Jun 8, 2026voice.mainwp.com is down2026h 44mResolved
Jun 6, 2026voice.mainwp.com is down2078h 8mResolved

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 MainWP 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 MainWP 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 MainWP 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 MainWP outage in this window ran 86d 14h, against a mean recovery of 59d 17h. If you depend on MainWP 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.