Kinsta Outage History

Kinsta experienced degraded performance issues with their MyKinsta dashboard for 3.9 hours. The incident affected users' ability to access and use the MyKinsta management interface properly. The performance issues were successfully resolved after investigation and remediation efforts.

Kinsta experienced a service disruption at their Sydney (AU) data center that affected some hosted websites for 33 minutes. The incident impacted website availability for customers using that data center location. Engineers successfully restored full service to all affected sites and advised customers to contact support if issues persisted.

Kinsta experienced a 20.5-hour incident where MyKinsta Analytics data including Visits, Bandwidth, and CDN Bandwidth was not being properly logged or displayed. The MyKinsta analytics servers were affected, preventing users from accessing current analytics information. The issue was identified and a solution was implemented, with full data restoration taking additional time to populate back into the analytics system.

Kinsta experienced a Cloudflare verification loop issue that prevented users from accessing phpMyAdmin for database management on certain sites. The problem lasted 1 hour and completely blocked database access through the phpMyAdmin interface. A fix was implemented and the incident was resolved after monitoring confirmed the solution was working.

Kinsta's MyKinsta dashboard experienced significant performance issues for 6.2 hours, with some pages failing to load or loading incompletely. The service team implemented a fix and monitored the results before confirming full resolution of the incident.

Kinsta experienced a major service disruption affecting their MyKinsta control panel, with users reporting significant performance issues that prevented normal access and functionality. The incident lasted 9.6 hours, during which engineers investigated the root cause, implemented a fix, and monitored the system for stability. The service was fully restored and declared resolved after confirming normal operations were maintained.

Kinsta experienced a bug in MyKinsta where the search and replace action would automatically run when users changed their primary domain, even when the "run search and replace" checkbox was unchecked. The issue affected the MyKinsta platform and persisted for approximately 15 days before being resolved. A fix was implemented and monitored to ensure the search and replace functionality now properly respects the checkbox setting.

Kinsta experienced a 5.6-hour service incident where critical MyKinsta actions including backups, restores, and new WP-Admin user creations were failing. The MyKinsta dashboard was affected, preventing users from performing essential website management tasks. The issue was identified and fixed, with users advised to retry previously failed actions.

Kinsta experienced issues with their chat support system where messages were delayed or failed to send entirely. The incident affected the Kinsta support system, impacting customers' ability to communicate with support representatives. The issue was resolved after 1.1 hours of investigation.

Kinsta experienced a 15.5-hour outage affecting their MyKinsta analytics servers, preventing the logging of key analytics data including visits, bandwidth, requests, and request paths. The issue was resolved after Cloudflare implemented a fix, restoring normal analytics functionality. The service has returned to normal operation with continued monitoring to ensure stability.