Live

MyKinsta Support System Unavailable

0

The MyKinsta support system is unavailable. Kinsta reports that the incident is resolved. The outage lasted 51 minutes.

State

Resolved

Started

Lasted

51 min

Worst impact

Major outage

Timeline

4 updates
19:1019:2319:3619:4920:02
Major outageDegradedUpdate postedTimes in UTC

Investigating

7 min 14%

Identified

27 min 52%

Monitoring

17 min 33%

Updates

Times in UTC

As posted by Kinsta

Resolved

We have continued to observe normal operations and will mark this incident as resolved. We do apologize for any difficulties you experienced attempting to reach our support team.

Monitoring

We are observing normal operations again. We will continue to monitor the situation. If you are still having issues reaching our Support team in MyKinsta, please email support@kinsta.com

Identified

Intercom has updated their status page to reflect the outages: https://www.finstatus.com/us-hosting/incidents/01M7JWJJY3RSVWY208SZDTMK05 We are continuing to monitor the situation and will post updates as they become available.

Investigating

Our support system is not currently available. We are working to resolve the issue as quickly as possible.

Affected components

1
Kinsta support system

Kinsta in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

20

Median duration

7 h 21 min

This incident

88% 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 21 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