Live

Sudden fatal errors

This incident has been resolved.

The latest update from Kinsta.

State

Resolved

Started

74 d ago

2026-08-20 06:26 UTC

Lasted

4 h 2 min

until 2026-08-20 10:28 UTC

Worst impact

Notice

Timeline

3 updates
06:2607:2708:2709:2810:28
NoticeUpdate postedTimes in UTC

Investigating

4 h 2 min 100%

Updates

Times in UTC

As posted by Kinsta

Resolved2026-08-20 10:28 UTC

This incident has been resolved.

Investigating2026-08-20 08:23 UTC

A hotfix has been released (WP Rocket v3.23.2.2). They are monitoring feedback from users to ensure the situation is completely solved. https://status.wp-rocket.me/

Investigating2026-08-20 06:26 UTC

Incompatibility between WP Rocket and latest WordPress version is causing 500 errors and bringing the site down. You can disable WP Rocket from MyKinsta and subscribe to their status page to get updates when the issue is resolved. https://status.wp-rocket.me/

Kinsta in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

13

Days with an incident

29

Median duration

6 h 27 min

This incident

37% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

17 days
median 6 h 27 min
90 days agoToday

Other Kinsta incidents

All incidents

Follow Kinsta

Your coding agent knows when Kinsta is down, and tells you when a failure is theirs, not yours. You can also get Kinsta incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "kinsta" and tell me if Kinsta has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=kinsta
Slack
/feed subscribe https://outages.cc/feed.xml?providers=kinsta

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane