Live

Temporary Performance Degradation

0

Kinsta reports temporary performance degradation at several data centers across its platform. Kinsta completed the emergency updates network-wide and marked the incident resolved. The outage lasted 1 hour and 49 minutes.

State

Resolved

Started

Lasted

1 h 49 min

Worst impact

Notice

Timeline

3 updates
18:2318:5019:1819:4520:12
NoticeUpdate postedTimes in UTC

Identified

1 h 49 min 100%

Updates

Times in UTC

As posted by Kinsta

Resolved

Our Engineering team has confirmed the successful rollout of the emergency updates. Any ongoing performance concerns are no longer attributed to this rollout, and we are therefore marking this incident as resolved. Thank you again for your patience throughout this incident, and we do apologise for any disruption experienced as a result.

Identified

Our Engineering team are applying updates to the last few remaining containers and expects this to be completed shortly. Thank you for your continued patience through this.

Identified

Our Engineering team is aware of temporary performance degradation affecting several data centers across our platform as emergency updates are rolled out network-wide. We apologise for any disruption this may cause.

Kinsta in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

14

Days with an incident

21

Median duration

7 h 23 min

This incident

75% shorter than the median

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

4 days
median 7 h 23 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.live/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.live/feed.xml?providers=kinsta
Slack
/feed subscribe https://outages.live/feed.xml?providers=kinsta

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane