outages.live
Live

Kinsta

Kinsta is operational

Checked 28 s ago Operational

History

90 days agoToday

Incidents in 90 days

13

Days with an incident

29

Median duration

6 h 27 min

Longest incident

17 days

Components

58
Affiliate Dashboard Operational
90 days agoNo incidentsToday
Cloudflare Integration Operational
90 days agoNo incidentsToday
Kinsta.com Operational
90 days agoNo incidentsToday
Kinsta API Operational
90 days agoNo incidentsToday
Kinsta CDN Operational
90 days agoNo incidentsToday
Kinsta DNS Operational
90 days agoNo incidentsToday
Kinsta support system Operational
90 days agoNo incidentsToday
MyKinsta Operational
90 days ago22 days with an incidentToday
MyKinsta analytics servers Operational
90 days agoNo incidentsToday
Outbound Email System Operational
90 days agoNo incidentsToday
Amsterdam, Netherlands data center Operational
90 days agoNo incidentsToday
Ashburn, Virginia, US data centers Operational
90 days ago3 days with an incidentToday
Batam, Indonesia data center Operational
90 days agoNo incidentsToday
Bogotá, Colombia data center Operational
90 days agoNo incidentsToday
Changhua County, Taiwan data center Operational
90 days agoNo incidentsToday
Chicago, Illinois, US data center Operational
90 days agoNo incidentsToday
Columbus, Ohio, US data center Operational
90 days agoNo incidentsToday
Council Bluffs, Iowa, US data center Operational
90 days agoNo incidentsToday
Dallas, Texas, US data center Operational
90 days agoNo incidentsToday
Dammam, Saudi Arabia data center Operational
90 days agoNo incidentsToday
Delhi, India data center Operational
90 days agoNo incidentsToday
Dubai, United Arab Emirates data center Operational
90 days agoNo incidentsToday
Eemshaven, Netherlands data center Operational
90 days agoNo incidentsToday
Frankfurt, Germany data centers Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration1 h 20 min03:48 to 05:07Downloadable Backup actions are stuck in processing status in the MyKinsta Dashboard.Degraded

This incident has been resolved.

Oct 26, 2026

Duration1 h 43 min18:13 to 19:56MFA emails not being sent for MyKinstaPartial outage

Following continued monitoring, we can confirm that MyKinsta email functionality has been operating normally, with no further issues observed. If you are still experiencing issues, please email us at support@kinsta.com.

Oct 23, 2026

Duration4 days13:19 to 14:06Information in regards to newly discovered PHP vulnerability CVE-2026-115560 (Oct 23, 2026)Notice

We can confirm that the mitigations have been successful and no compromises have occurred as a result of this. If you have any other questions, please contact our support team at support@kinsta.com.

Oct 21, 2026

Duration13 h 22 min19:04 to 08:26PHP Security Vulnerability UpdateNotice

All sites are protected, the PHP security updates have been rolled out across the platform, and we have no evidence of any breaches related to this vulnerability.

Oct 20, 2026

Duration15 h 28 min06:40 to 22:08Partial outage in London datacenterDegraded

The infrastructure has remained stable and this has been resolved.

Oct 8, 2026

Duration7 h 21 min14:42 to 22:03Service disruption at the Northern Virginia (US East 4) data centerPartial outage

This has been resolved.

Aug 27, 2026

Duration5 h 31 min16:43 to 22:14Service disruption at the Toronto (CA) data centerPartial outage

Service has remained stable in the Toronto (CA) data center. This issue is now resolved. If you are still seeing issues with your website please contact our support team. Thank you for your patience and we do apologize for any disruption to your business.

Aug 26, 2026

Duration7 h 25 min16:56 to 00:21MyKinsta performance degradationDegraded

This incident has been resolved.

Aug 20, 2026

Duration4 h 2 min06:26 to 10:28Sudden fatal errorsNotice

This incident has been resolved.

Aug 17, 2026

Duration5 h 29 min21:09 to 02:39Service disruption at the Northern Virginia (Ashburn) data centerPartial outage

This incident has been resolved.

Aug 16, 2026

Duration3 h 29 min17:52 to 21:21Service disruption at the Phoenix, AZ (us-phoenix-1) data centerPartial outage

The server has remained stable since the fix was implemented. The issue is resolved at this time. If you do have any questions please do not hesitate to reach out to our Support team.

Aug 11, 2026

Duration17 days09:02 to 19:10Mykinsta file manager issue with uploading larger filesDegraded

We have determined that this is caused by an update to our network firewall systems for security. We will continue to explore other options for allowing larger uploads through MyKinsta, but at this time, files larger than 500MB should now only be uploaded via SFTP. If you have any other questions, please contact our support team via chat from your MyKinsta dashboard, or by emailing us at support@kinsta.com.

Maintenance

MyKinsta Maintenance

MyKinsta and support chat will be unavailable while we perform maintenance. We have scheduled two hours for the outage, but we may be able to complete the maintenance sooner. Your websites and other services will not be affected. If you need to contact support during the maintenance period, you can email support@kinsta.com. Our Resource Center documentation is also available to answer many questions: https://kinsta.com/docs/ We will post any necessary updates here on the status page.

Maintenancestarts in 2 d

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane