System status

All times are US/Pacific (PST)

May 20, 2017

Google Cloud US Based VM Instance Issue

Resolved

Our engineers are investigating the issue.

Updates

The issue has been resolved.

April 24, 2017

Intermittent Connectivity on Load Balancer

Resolved

One of our load balancers is producing intermittent connectivity issues which is affecting a small number of sites. We hope to have this resolved soon. We apologize for the inconvenience.

Updates

April 24, 11:30 am

This has now been resolved.

April 05, 2017

Dashboard Updates

Resolved

Our engineers are performing updates on the My.kinsta dashboard. We’re deeply sorry for any inconveniences. We’re working hard on getting it back online soon. Thank you for your patience.

Updates

Updates have been successfully completed. Thank you for your patience.

March 30, 2017

Google Cloud US Based VM Instance Degraded Performance

Resolved

Our engineers are investigating the issue.

Updates

This incident has been resolved.

March 29, 2017

Intermittent Connectivity on Google Cloud US Based VM Instance

Resolved

We are investigating reports of an issue with one of our US based Google Cloud Compute Engine instances.

Updates

The issue has been quickly resolved. Sorry for the inconvenience.

March 15, 2017

Google Compute Engine Experiencing Disruption

Resolved

We are investigating reports of an issue with one of our US based Google Cloud Compute Engine instances. We will publish an update as soon as we know more.

Updates

March 15, 1:00 pm

Google Compute Engine instances in us-central zones are experiencing a networking issue. Incident #17006

March 15, 2:12 pm

Google Compute Engine services has restored internet connectivity. They are taking necessary actions to prevent a recurrence. We apologize for the inconvenience.

March 14, 2017

Intermittent Connectivity on Load Balancer

Resolved

One of our load balancers was producing intermittent connectivity issues for a number of sites. This was resolved within 15 minutes. We apologize for the inconvenience.

March 14, 2017

AWS slow DNS propagation

Resolved

AWS is currently investigating slow propagation of DNS edits to the Route 53 DNS servers.

Record changes are propagating, while they work through the backlog of pending changes that have accumulated. They expect full recovery to take several more hours. They are continuing to throttle ChangeResourceRecordSets API calls.
Queries to existing DNS records remain unaffected.

For more details, please visit Amazon’s status page: https://status.aws.amazon.com/.

Adding new sites on the Kinsta dashboard is disabled until AWS resolves the issue, please contact our support for further help.

Updates

March 14, 2:54 pm

All DNS update operations are now completing successfully. The ability to add new sites on the Kinsta dashboard has now been restored.

February 28, 2017

AWS Outage

Resolved

Earlier this morning Amazon Web Services started experiencing outages in some regions. Due to many services, plugins, and dependencies relying on Amazon, this may result in scripts and or timeouts on your WordPress site.

Amazon is actively working on restoring services, you can see more here:
https://status.aws.amazon.com/

Updates

AWS has restored services across most regions. We will continue to monitor the status.

The issue has now been resolved by AWS.

February 15, 2017

DDoS Attack

Resolved

We are aware of a massive DDoS attack which is targeting our infrastructure.

Updates

It took a few minutes but we’ve stabilized now and everything is back to normal.

January 20, 2017

Google Cloud EU Load Balancer Outage

Resolved

One of our Google Cloud EU based load balancer instance’s host machine has shut down unexpectedly, and had to be restarted on a new host machine. Google Cloud usually live migrates instances from one host machine to another without downtime, however this was a serious hardware failure which didn’t allow the process to complete in time. The new load balancer instance was up and running 4 minutes after our engineers have been notified and after running the necessary tests to ensure its consistency it began serving requests 7 minutes after the initial compute.instances.hostError event. We apologize for the inconvenience.

December 16, 2016

Google Cloud US-based Load Balancer

Resolved

One of our load balancers was overwhelmed and we resolved the issue as soon as possible. The downtime was around 5 minutes and our engineers have made the necessary steps to avoid such instances in the future. We apologize for the inconvenience!

Updates

The issue has been resolved.