Yoast Outage History

Yoast degraded · 1 active incident View live status →

Pingoru has recorded 3 incidents for Yoast: 3 in the last 12 months and 1 in the last 90 days.

Source: status.yoast.com

3incidents recorded
3last 12 months
1last 90 days
68 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking Yoast in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026118 of 533 (3%)

Incidents, newest first

Critical June 29, 2026 website yoast.com is down 1h 3m yoast.com

Started Jun 29, 2026, 02:32 PM UTC· resolved Jun 29, 2026, 03:36 PM UTC

  1. investigating Jun 29, 2026, 02:32 PM UTC

    We are currently seeing problems with our website yoast.com. We are investigating the problem at the moment.

  2. identified Jun 29, 2026, 02:43 PM UTC

    The issue has been identified are implementing a fix.

  3. identified Jun 29, 2026, 02:47 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Jun 29, 2026, 03:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 29, 2026, 03:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 20, 2026 my.yoast.com down 1h 13m my.yoast.com

Started Jan 20, 2026, 08:52 AM UTC· resolved Jan 20, 2026, 10:05 AM UTC

  1. investigating Jan 20, 2026, 09:20 AM UTC

    We are currently seeing problems with the service my.yoast.com. Customers will not be able to login to myYoast. We are investigating the problem at the moment.

  2. monitoring Jan 20, 2026, 09:28 AM UTC

    The problem has been found and a fix has been applied. Service my.yoast.com is available again. We will keep monitoring the solution.

  3. resolved Jan 20, 2026, 10:05 AM UTC

    This incident has been resolved.

Read the full incident report →