Temporary Performance Degradation
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 updatesIdentified
1 h 49 min 100%
Updates
Times in UTCAs posted by Kinsta
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.
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.
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 historyIncidents in 90 days
14
Days with an incident
21
Median duration
7 h 23 min
This incident
75% shorter than the median
Other Kinsta incidents
All incidentsKinsta·Mykinsta - backup restore issue
Backup restores do not work in Kinsta MyKinsta. Kinsta reports that the issue is resolved and that backup restores now complete successfully. The outage lasted about 12 hours and 12 minutes.
Kinsta·WP Admin auto-login from MyKinsta unavailable
The WP Admin auto-login from MyKinsta does not work. Kinsta reports that the incident is resolved. It lasted about 6 hours.
Kinsta·MyKinsta service disruption
The MyKinsta service disruption affected MyKinsta, the Outbound Email System, site creation, SSH access and SFTP access. Kinsta reports that the incident is resolved. It lasted about 17 hours and 34 minutes.
Kinsta·MyKinsta Support System Unavailable
The MyKinsta support system is unavailable. Kinsta reports that the incident is resolved. The outage lasted 51 minutes.
Kinsta·Downloadable Backup actions are stuck in processing status in the MyKinsta Dashboard.
This incident has been resolved.
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.
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.
https://outages.live/feed.xml?providers=kinsta/feed subscribe https://outages.live/feed.xml?providers=kinstaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane