Yoast Outage History

6 incidents recorded over the last 365 days, 3 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 Yoast Incident

Yoast incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 22, 2026Degraded performance of Yoast.comThis incident has been resolved.7h 4mResolved
Jun 29, 2026website yoast.com is downThis incident has been resolved.1h 3mResolved
Mar 1, 2026Scheduled maintenanceThe scheduled maintenance has been completed.30 minScheduled
Feb 16, 2026Yoast.com maintenance and upgradesMaintenance postponed.4h 0mScheduled
Feb 15, 2026Scheduled maintenanceThe scheduled maintenance has been completed.30 minScheduled
Jan 20, 2026my.yoast.com downThis incident has been resolved.1h 13mResolved

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 Yoast 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 Yoast 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 Yoast 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 Yoast outage in this window ran 7h 4m, against a mean recovery of 2h 23m. If you depend on Yoast 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.