New Multi-region uptime checks and custom-domain status pages

Kinsta Outage History

Daily provider-status observations and published incident history for Kinsta.

Operational

Kinsta is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Kinsta for future changes.

89.9% of 69 verified observed days had no reported provider issue

90-Day Trend

Aug 18Nov 15

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
October 2026 90% 30 3

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Aug 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

October 2026
MFA emails not being sent for MyKinsta
major Observed active window 1h 46m

View incident details and source

Started:

MyKinsta
monitoring
We have identified the issue as being with our upstream email provider, and a fix has been implemented. Please attempt to log in again if you were not receiving the MFA emails previously. We have been notified by our internal teams that the emails were queued and are being sent first, so there may be some delay in emails being sent until those can be processed. If you are still experiencing issues, please email us at support@kinsta.com.
investigating
We are investigating issues with MFA emails for login requests that are not being sent.
Partial outage in London datacenter
minor Observed active window 15h 30m

View incident details and source

Started:

London, United Kingdom data centers
monitoring
All sites of the affected hosting machines are now back up and we're monitoring.
identified
Due to a power event, our infrastructure provider had suffered an outage within europe-west2-b zone. The power event is mitigated. Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after. https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj
identified
There's a status page posted by our infrastructure provider and we are waiting for resolution: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj
identified
It has been confirmed that the issue is origination from our cloud infrastructure provider. Their engineering team is working on providing a solution.
investigating
We are currently investigating issues in London datacenter. It's a partial outage and our engineers are looking into it.
Service disruption at the Northern Virginia (US East 4) data center
major Observed active window 7h 22m

View incident details and source

Started:

Ashburn, Virginia, US data centers
monitoring
A fix has been implemented and we are monitoring the results. If your site was affected and is still experiencing difficulties, please contact our support team via chat in MyKinsta, or by emailing support@kinsta.com.
identified
We have identified the cause of the issue, and we are currently working on a fix.
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Northern Virginia (US East 4) data center. We are working to restore service to affected sites as quickly as possible.
August 2026
Service disruption at the Toronto (CA) data center
major Observed active window 5h 31m

View incident details and source

Started:

Toronto, Ontario, Canada data centers
monitoring
Our Engineers have implemented a solution. We are now monitoring the service to ensure its ongoing stability. We appreciated your patience and apologize again for the disruption this caused. If you do have any questions or are continuing to see any issues please do not hesitate to contact our Support team.
identified
Our Engineers are continuing to work on a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
identified
Our team is continuing to work on implementing a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
identified
Our team is continuing to work on implementing a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
identified
Our Engineers are continuing to work on a solution. We appreciate your continued patience. If you do have any questions please do not hesitate to contact our Support team.
identified
Our team is working on implementing a solution. We appreciate your patience and apologize for this disruption. If you do have any questions please do not hesitate to contact our Support team.
investigating
Our engineers are continuing to work towards a solution. We appreciate your patience and apologize for this disruption. If you do have any questions please do not hesitate to contact our Support team.
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Toronto (CA) data center. We are working to restore service to affected sites as quickly as possible.
MyKinsta performance degradation
minor Observed active window 7h 29m

View incident details and source

Started:

MyKinsta
monitoring
We have implemented a fix and we are monitoring the results.
investigating
We are currently investigating issues with MyKinsta's performance, particularly when switching between accounts for users with multiple company accounts.
Mykinsta file manager issue with uploading larger files
minor Observed active window 418h 7m

View incident details and source

Started:

MyKinsta
investigating
Our investigation is still underway and is likely to continue into next week. We thank you for your continued patience.
investigating
The issue is still being investigated by our engineers. We appreciate your continued patience.
investigating
We are still investigating the issue, thank you for your continued patience.
investigating
We are still investigating the issue, thank you for your continued patience.
investigating
We are still investigating the issue, thank you for your continued patience.
investigating
We are still investigating the issue, thank you for your continued patience.
investigating
We are still investigating the issue, thank you for your continued patience.
investigating
The issue is still being investigated by our engineers. We appreciate your continued patience.
investigating
The issue is still being investigated by our engineers. We appreciate your continued patience.
investigating
The issue is still being investigated by our engineers.
investigating
The issue is still being investigated by our engineers.
investigating
We are still investigating the issue. Thank you for your patience.
investigating
We are still investigating the issue. Thank you for your patience.
investigating
We are still investigating the issue. Thank you for your patience.
investigating
Our engineers are continuing to investigate into the issue. We apologize for any inconvenience this causes.
investigating
Our engineers are continuing to investigate into the issue. We apologize for any inconvenience.
investigating
Our engineers are continuing to investigate into the issue. We apologize for any inconvenience.
investigating
The issue is still being investigated by our engineers.
investigating
We are continuing to investigate the issue and apologize for the inconvenience.
investigating
We are continuing to investigate the issue.
investigating
We are continuing to investigate the issue.
investigating
We are continuing to investigate the issue.
investigating
We are continuing to investigate the issue.
investigating
We are continuing to investigate the issue.
investigating
We are currently investigating reports of issues with uploading larger files (100+ MB).

Legacy Incident Archive

31 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

March 2026
Search and Replace bug when changing the primary domain in MyKinsta
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are continuing to work on a fix for this issue.
identified
We continue to actively work on a solution to this issue.
identified
We continue to actively work on a solution to this issue.
identified
We continue to actively work on a solution to this issue.
identified
We are continuing to work on the fix for this issue.
identified
We continue to actively work on a solution to this issue.
identified
We continue to actively work on a solution to this issue.
identified
We continue to actively work on a solution to this issue.
identified
We are actively working on a solution to this issue.
identified
We are actively working on a solution to this issue.
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
We have identified the issue and are actively working on implementing a fix.
investigating
We are continuing to investigate this issue.
investigating
We are still investigating the issue.
investigating
This bug has been reported to our MyKinsta development team. We will continue to provide updates as soon as it becomes available.
investigating
We are experiencing a bug where the search and replace action continues to run when changing the primary domain, even if the "run search and replace" checkbox is unchecked. We are currently investigating this issue.