Kinsta
Infrastructure. Source: Kinsta status page.
- Incidents, last 90 days
- 10
- Median duration
- 5h 59m
- p95 duration
- 17d 10h
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| A zone, region or data center became unavailable | 6 |
| A provider or third-party service this vendor depends on failed | 2 |
| The text does not say enough to tell | 1 |
| A configuration change caused the failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Partial outage in London datacenter
Affected: London, United Kingdom data centers
Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are currently investigating issues in London datacenter. It's a partial outage and our engineers are looking into it.
-
identified
It has been confirmed that the issue is origination from our cloud infrastructure provider. Their engineering team is working on providing a solution.
-
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
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....
-
monitoring
All sites of the affected hosting machines are now back up and we're monitoring.
-
resolved
The infrastructure has remained stable and this has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Northern Virginia (US East 4) data center
Affected: Ashburn, Virginia, US data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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.
-
identified
We have identified the cause of the issue, and we are currently working on a fix.
-
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.
-
resolved
This has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Toronto (CA) data center
Affected: Toronto, Ontario, Canada data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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.
-
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.
-
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.
-
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.
-
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...
-
resolved
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.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta performance degradation
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating issues with MyKinsta's performance, particularly when switching between accounts for users with multiple company accounts.
-
monitoring
We have implemented a fix and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Sudden fatal errors
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Incompatibility between WP Rocket and latest WordPress version is causing 500 errors and bringing the site down. You can disable WP Rocket from MyKinsta and subscribe to their status page to get updates when the issue is resolved. https://status.wp-rocket.me/
-
investigating
A hotfix has been released (WP Rocket v3.23.2.2). They are monitoring feedback from users to ensure the situation is completely solved. https://status.wp-rocket.me/
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Northern Virginia (Ashburn) data center
Affected: Ashburn, Virginia, US data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Northern Virginia (Ashburn) data center. We are working to restore service to affected sites as quickly as possible.
-
investigating
We are actively investigating this issue and sincerely apologize for any inconvenience it may cause.
-
identified
Our Systems Engineering team is currently working on a solution for this issue. We will provide updates as soon as they are available.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
identified
We are currently investigating an issue causing some sites to return 520 errors. Our Engineering team has identified the cause and is working on fixing the affected sites. We will provide updates as we continue to work on the issue.
-
monitoring
The issue causing some sites to return 520 errors has been fixed. Our Engineering team is continuing to monitor the affected sites to make sure everything remains stable.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Phoenix, AZ (us-phoenix-1) data center
Affected: Phoenix, Arizona, US data center
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Phoenix, AZ (us-phoenix-1) data center. We are working to restore service to affected sites as quickly as possible.
-
monitoring
Our engineers have implemented a fix. We do see service appears to be restored at this point. We are continuing to monitor the server to ensure its ongoing stability. We do apologize about the disruption and impact this caused to your business. If you do have any questions...
-
resolved
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.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Mykinsta file manager issue with uploading larger files
Affected: MyKinsta
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating reports of issues with uploading larger files (100+ MB).
-
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 continuing to investigate the issue and apologize for the inconvenience.
-
investigating
The issue is still being investigated by our engineers.
-
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
Our engineers are continuing to investigate into the issue. We apologize for any inconvenience this causes.
-
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
The issue is still being investigated by our engineers.
-
investigating
The issue is still being investigated by our engineers.
-
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
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
Our investigation is still underway and is likely to continue into next week. We thank you for your continued patience.
-
resolved
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...
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Frankfurt (DE) data center
Affected: Frankfurt, Germany data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting sites on a server in the Frankfurt (DE) data center. We are working to restore service to affected sites as quickly as possible.
-
investigating
We are continuing to investigate into the cause of the issue. We appreciate your patience while we work on resolving this issue as soon as possible. If you have any questions please do not hesitate to reach out to our Support team.
-
investigating
Our team is continuing to make progress towards a solution. We appreciate your continued patience while we work on resolving this issue as soon as possible. If you have any questions please do not hesitate to reach out to our Support team.
-
identified
Our team is in the process of implementing a solution to restore service as soon as possible. We appreciate your patience and understanding while we work to restore service to the affected server. If you have any questions please do not hesitate to reach out to our Support team.
-
identified
Our team is continuing to make progress on restoring full service to the affected server. We will provide updates as they become available. If you have any questions please do not hesitate to reach out to our Support team.
-
identified
Our team is working as quickly as possible on implementing a solution. We appreciate your continued patience and will provide updates as they become available.
-
monitoring
Our Engineers have successfully restored full service to all affected sites in the Frankfurt (DE) data center. We are continuing to monitor the server to ensure it's ongoing stability. If you are still seeing issues with your website please contact our support team. Thank you...
-
resolved
The server has remained stable since the solution was implemented. The incident is resolved at this time. If you have any questions or are continuing to see any issues please do not hesitate to reach out to our Support team. We are available 24/7 and always happy to help.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta Support System Messages Delayed
Affected: Kinsta support system
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our support system is currently experiencing significant message delays. We are working to resolve the issue as quickly as possible.
-
identified
We've identified the issue as being with our upstream provider, Intercom. We are reaching out to them to resolve this.
-
identified
Intercom has updated their status page for this issue: https://www.finstatus.com/us-hosting
-
identified
We are continuing to work on a fix for this issue with our support system provider.
-
identified
Intercom is currently working on a resolution for this issue, and we will update again once that is in place.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Eemshaven (NL) data center
Affected: Eemshaven, Netherlands data center
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Eemshaven (NL) data center. We are working to restore service to affected sites as quickly as possible.
-
monitoring
Our Engineers have implemented a solution. We are continuing to monitor the region to ensure its ongoing stability 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...
-
resolved
Our Engineers have successfully restored full service to all affected sites in the Eemshaven (NL) data center. 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.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Amsterdam (NL) data center
Affected: Amsterdam, Netherlands data center
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting sites in the Amsterdam (NL) data center. We are working to restore service to affected sites as quickly as possible.
-
identified
Our Engineers have identified that the issue is caused by our upstream provider for one of our compute instances. We are continuing to follow the situation and will provide further updates as they become available.
-
identified
We are continuing to work with our upstream cloud provider. Thank you for your continued patience.
-
monitoring
Our Engineers have confirmed that service has been successfully restored to all affected sites in the Amsterdam (NL) data center. We are monitoring for any further issues. If you are still seeing issues with your website, please contact our Support team. Thank you for your...
-
resolved
Our Engineers have confirmed again that service has been successfully restored to all affected sites in the Amsterdam (NL) data center. This incident is now fully resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta degraded performance
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of performance issues with our control panel, MyKinsta. We are working on restoring normal service to MyKinsta as quickly as possible.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
After monitoring the situation, our Engineers have confirmed that full service has remained to our control panel, MyKinsta. If you are still unable to log into MyKinsta, please contact our support team by sending an email to support@kinsta.com. We do apologize for any...
Excerpts are shortened. Read the full incident on Kinsta's status page.
Mykinsta dashboard issues
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating a number of reports of failed actions (backups, push action, etc.) in Mykinsta.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Issues in Amsterdam data center
Affected: Amsterdam, Netherlands data center
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating performance issues for sites hosted in Amsterdam datacenter. This isn't affecting all sites in datacenter, it's limited to a number of sites and our team is working on it.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta dashboard login issues
Affected: MyKinsta
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating reports for new sessions in MyKinsta dashboard where the login to our dashboard is hanging. We will provide updates as soon as they become available.
-
identified
The issue has been identified and a fix is being implemented.
-
investigating
The fix we attempted to deploy didn't work, we are continuing to investigate this further on our end. We will provide updates as soon as they become available! Thanks for your understanding and patience.
-
investigating
Our Engineering team has identified that this is impacting other MyKinsta-related actions, such as creating new environments and adding domains to environments. We are continuing to investigate this issue. Thank you for your continued patience.
-
investigating
Our Engineering team are continuing to investigate the issue. If you require assistance and are unable to log into MyKinsta, please reach out to our Support team by emailing support@kinsta.com.
-
investigating
Our Engineering team are continuing to investigate the issue.
-
investigating
MyKinsta will be completely unavailable while our Engineering team continue to focus on resolving this issue. Websites are not impacted by this MyKinsta outage. Thank you for your continued patience.
-
investigating
Our Engineering team are continuing to investigate the issue as a priority.
-
monitoring
Our Engineering team has implemented a solution and is currently monitoring the results.
-
monitoring
MyKinsta has remained fully operational since the solution was deployed. We will continue to monitor the situation.
-
resolved
MyKinsta has remained operational during our monitoring, and as such, we will mark this incident as resolved. Thank you for your patience throughout this, and we do apologize for any issues you experienced attempting to access MyKinsta.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the London data center
Affected: London, United Kingdom data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our Engineers are investigating reports of a service disruption affecting some sites in the London data center. We are working to restore service to affected sites as quickly as possible.
-
identified
Our Engineers are continuing to investigate the issue.
-
identified
Our Engineers are continuing to investigate the issue.
-
identified
Our Engineers are continuing to investigate the issue. We apologize for the inconvenience.
-
resolved
Our Engineers have successfully restored full service to all affected sites in the London (UK) data center. 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.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Issues in Amsterdam data center
Affected: Amsterdam, Netherlands data center
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating the issues in Amsterdam data center.
-
monitoring
The affected hosting machines are booting up, the sites are now online and we're monitoring.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Amsterdam datacenter outage
Affected: Amsterdam, Netherlands data center
Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Some servers in the Amsterdam datacenter are not reachable. We are currently working with our provider to determine a cause and resolve this as quickly as possible.
-
monitoring
A fix has been implemented by our datacenter provider and we are monitoring the results.
-
resolved
We've confirmed all sites are once again reachable. If you have any other questions, please reach out to our support team via chat, or by emailing us at support@kinsta.com.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Bot Management - Increased False Positives
Affected: Cloudflare Integration
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
monitoring
Our service partner, Cloudflare, is currently experiencing an issue in which certain legitimate requests are being incorrectly assigned a low bot score. As a result, some requests may be blocked by our Bot Protection feature if it is enabled on the site. A fix has been released,...
-
monitoring
We are continuing to monitor the situation. Thank you for your patience.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Localized CDN issues (Jerusalem data center)
Affected: Kinsta CDN
Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
investigating
We have received reports of issues with CDN that affects sites hosted in Jerusalem data center. Enabling CDN might cause layout issues on the site. We are investigating the issue.
-
monitoring
We have released a hotfix for .il TLDs to mitigate this issue while we await Cloudflare's full resolution of the incident. Thank you for your patience. https://www.cloudflarestatus.com/incidents/vjbxys0gy9bb
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Domains cannot be added to Mykinsta sites
Affected: MyKinsta
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
identified
There's an Custom Hostname API issue on Cloudflare which is preventing the domains from being added in Mykinsta. https://www.cloudflarestatus.com/incidents/59gsh0xrh6gg
-
identified
Cloudflare has now updated its status page to confirm that they have identified the issue and is working on a fix. We will provide further updates here as they become available.
-
identified
We are continuing to monitor the situation. Thank you for your patience.
-
identified
Adding new Domains to MyKinsta may occasionally fail. We are monitoring the situation continuously. Thank you for your patience.
-
monitoring
Cloudflare has released a fix, and we are continuously monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Site creation failing in Mykinsta
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating the issue of site creation failing.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Mykinsta dashboard issues
Affected: MyKinsta
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are currently investigating issues with Mykinsta dashboard. If you need to contact the support team in the meantime, please email support@kinsta.com.
-
identified
We have identified the root cause of the dashboard inaccessibility. The issue stems from a disruption with our Apollo GraphQL integration. We are actively working together with the Apollo team to resolve the issue and restore full access as quickly as possible.
-
monitoring
We have deployed a temporary workaround that should restore dashboard access for most users, but the underlying issue is not yet fully resolved and may surface again. We are continuing to work toward a permanent fix.
-
monitoring
A permanent fix has been successfully deployed, and dashboard access is fully restored. We are now monitoring the platform closely to ensure long-term stability and to confirm that the integration with Apollo GraphQL remains stable.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Downloadable/External backups service disruption.
Affected: Kinsta.com
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating timeout issues related to downloadable and external backups. This feature is temporarily disabled while we continue our investigation. We apologize for the inconvenience.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Errors on Domains page or when adding domains in MyKinsta
Affected: Cloudflare Integration, MyKinsta
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
identified
We are seeing a number of errors on the Domains page for sites in MyKinsta, and errors when attempting to add domains. Upon further investigation we determined this is due to an API outage at Cloudflare: https://www.cloudflarestatus.com/incidents/znll7lfnd35h They are currently...
-
identified
Errors when attempting to add domains are affecting site and staging environment creations as well; this will also be resolved when Cloudflare's fix is in place: https://www.cloudflarestatus.com/incidents/znll7lfnd35h
-
monitoring
A fix has been implemented; please re-try any previously failed actions in MyKinsta and contact support if you are still experiencing difficulties.
-
resolved
This has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta analytics system service disruption
Affected: MyKinsta analytics servers
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our Engineers are investigating reports of performance issues with the analytics data reported in MyKinsta. We are working restore normal functionality to our analytics system as quickly as possible.
-
identified
We are continuing to look into the issue and are working towards a solution as soon as possible. If you do have any questions please do not hesitate to reach out to our Support team. We appreciate your patience in this matter.
-
identified
We’re continuing to investigate the reported performance issues affecting MyKinsta. Our team is looking into the cause and will share further updates as soon as we have more information.
-
identified
We’re continuing to investigate the reported performance issues affecting MyKinsta. Our team is looking into the cause and will share further updates as soon as we have more information.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved and all data is visible.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta service degraded performance
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of performance issues with our control panel, MyKinsta. We are working on restoring normal service to MyKinsta as quickly as possible. Thanks for your continued patience.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Mykinsta dashboard issues
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating an issue with degraded performance on Mykinsta.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Service disruption at the Sydney (AU) data center
Affected: Sydney, New South Wales, Australia data centers
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of a service disruption affecting some sites in the Sydney (AU) data center. We are working to restore service to affected sites as quickly as possible.
-
resolved
Our Engineers have successfully restored full service to all affected sites in the Sydney (AU) data center. 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.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Issue with MyKinsta Analytics data
Affected: MyKinsta analytics servers
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are investigating issues with Analytics data which might not be logged at the moment: Visits, Bandwidth, CDN Bandwidth. We'll provide updates as we make progress.
-
identified
We have identified the cause of the issue and a solution has been implemented. It will take some time for all data to become present in the analytics system.
-
identified
We are continuing to investigate this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Cloudflare verification loop on phpMyAdmin
Affected: Cloudflare Integration
Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
investigating
We are currently investigating issues with Cloudflare verification repeating in a loop when accessing phpMyAdmin on certain sites, effectively preventing database access via phpMyAdmin. We will provide updates as they come.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta performance degradation
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We're currently seeing reports of performance issues inside MyKinsta, with some pages not loading or not loading fully, and we're investigating these issues.
-
monitoring
We've implemented a fix and we're monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta service disruption
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of performance issues with our control panel, MyKinsta. We are working on restoring normal service to MyKinsta as quickly as possible.
-
monitoring
We've implemented a fix and we are monitoring the results.
-
identified
This issue is still ongoing. Our engineers are actively investigating and working toward a full resolution. We appreciate your patience and will provide another update as soon as more information becomes available.
-
monitoring
The issue has been resolved and services are now operating normally. We are continuing to monitor the situation to ensure stability.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Search and Replace bug when changing the primary domain in MyKinsta
Affected: MyKinsta
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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.
-
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 still investigating the issue.
-
investigating
We are continuing to investigate this issue.
-
identified
We have identified the issue and are actively working on implementing a fix.
-
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 are actively working on a solution to this issue.
-
identified
We are actively working 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 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 continuing to work on a fix for this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
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.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Failing actions in MyKinsta
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Some actions within MyKinsta, such as backups and restores or new WP-Admin user creations, are failing. We're currently investigating the cause.
-
identified
We have identified the issue and we are working on implementing a fix.
-
monitoring
A fix has been implemented for this. Please re-try any previously failed MyKinsta actions, and contact support via chat or by emailing support@kinsta.com if you are still experiencing any issues.
-
resolved
This has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Chat Support system issues
Affected: Kinsta support system
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently experiencing issues with message delivery in our chat system. Messages might be delayed or not sent. Thank you for your patience while we investigate this matter.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Issue with Analytics data
Affected: MyKinsta analytics servers
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
Names an upstream provider: Cloudflare.
-
investigating
We are investigating issues with Analytics data which might not be logged at the moment: Visits, Bandwidth, Requests, Request Path. We'll provide updates as we make progress.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been implemented by Cloudflare, and analytics should now be logging properly. We'll continue to monitor for the time being, but this appears to be resolved.
-
resolved
The MyKinsta analytics system has continued to operate normally. This issue is now resolved. If you are still experiencing issues while accessing analytics data in MyKinsta please contact our support team. We do apologize for any inconvenience caused by this disruption.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta analytics system service disruption
Affected: MyKinsta analytics servers
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our Engineers are aware of reports of performance issues with the analytics data reported in MyKinsta. We have identified the cause of the issue and a solution has been implemented. It will take some time for all data to become present in the analytics system. We appreciate your...
-
identified
We are still investigating this issue and apologize for any inconvenience it may have caused.
-
identified
We are still investigating this issue and apologize for any inconvenience it may have caused.
-
identified
At this time most analytics data should be available and displaying properly from within MyKinsta. However, additional time is needed for all cache related analytics data to become present. We appreciate your patience while our team works on fully resolving this matter. If you...
-
monitoring
Most analytics data is now up to date; however, our system is still backfilling the cache-related data in Analytics. We will continue to provide updates until all analytics data is fully up to date. Thank you for your continued patience.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta APM system service disruption
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of performance issues with the APM tool data reported in MyKinsta. We are working restore normal functionality to our system as quickly as possible.
-
investigating
We are still investigating this issue and apologize for any inconvenience it may have caused.
-
investigating
We are still investigating this issue and apologize for any inconvenience it may have caused.
-
investigating
We are still investigating the MyKinsta APM system service disruption, which leaves the tool partially operational. We are working on restoring the normal functionality.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta's Downloadable Backup actions are stuck.
Affected: MyKinsta
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are receiving reports that MyKinsta's downloadable backup actions are stuck in a pending status and are not completing. We are currently investigating this issue and apologize for any inconvenience it may have caused.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor the results of the fix
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta's Downloadable and External backups are currently undergoing maintenance.
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
monitoring
The Downloadable and External Backup features in MyKinsta will be unavailable due a planned maintenance. We hope to complete this maintenance within 30 minutes. We apologize for the inconvenience.
-
monitoring
This maintenance is still ongoing. Updates will be posted as soon as they become available.
-
resolved
This maintenance has been completed successfully.
Excerpts are shortened. Read the full incident on Kinsta's status page.
Downtime issues in London datacenter
Affected: London, United Kingdom data centers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
We are getting reports of downtime and performance issues for sites hosted in London datacenter. We are currently investigating the issue and will provide updates as we make progress.
-
investigating
Our investigation suggests that this might be related to our cloud provider and we are working with them to try and determine the cause so that we can start working on a solution.
-
identified
We have confirmed that this is related to an issue at our cloud provider, and we are working with them to reach a resolution.
-
identified
Our cloud provider is still working on a full resolution to this issue.
-
identified
Some sites may be coming back online, at least partially. This issue is still being worked on however, and is not fully resolved.
-
identified
We are continuing to see more sites come back online, and will continue to work on resolving any issues with the remaining sites, and monitor for stability.
-
monitoring
At this time we are seeing that service to all affected sites in the region should be restored. We are continuing to monitor the region to ensure ongoing service stability. If you are still seeing issues with your website please contact our support team. Thank you for your...
-
monitoring
We are continuously monitoring for any issues.
-
monitoring
We are continuing to monitor the region to ensure ongoing service stability. 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.
-
resolved
Service in the London (UK) data center has remained stable since the last update. The issue is now resolved at this time. 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...
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta APM service disruption
Affected: MyKinsta
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Application Performance Monitoring tool - APM is not showing any log data at this time. We are currently investigating this issue and apologize for the inconvenience.
-
monitoring
A fix has been implemented, and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta analytics system service disruption
Affected: MyKinsta analytics servers
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our Engineers are aware of reports of performance issues with the analytics data reported in MyKinsta. We have identified the cause of the issue and are implementing a fix. Analytics data maybe delayed by a few hours during this time until the solution is fully implemented. We...
-
identified
Our engineering team is continuing to implement a fix to restore full functionality to the Analytics system. While the solution is being deployed, you may continue to see delayed metrics in your dashboard. We expect this remediation to continue throughout the next day. If you do...
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta's Company Analytics page is currently unavailable.
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
The MyKinsta Company Analytics page is currently unavailable and redirects to the Dashboard homepage. We are investigating this issue and apologize for the inconvenience.
-
investigating
Our developers are still investigating the issue. We will provide updates as we make progress.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta APM service disruption
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
Our Engineers are investigating reports of performance issues with the APM data reported in MyKinsta. At this time APM data may not be displayed in MyKinsta. We have identified the cause of the issue and are working to restore normal functionality to our APM system as quickly as...
-
monitoring
A fix has been implemented and APM data should be displaying in MyKinsta again. We will continue to monitor the service to ensure its ongoing stability.
-
monitoring
We are continuing to monitor the situation for any additional issues.
-
monitoring
We are continuously monitoring for any issues.
-
resolved
After further monitoring, our Engineers have confirmed this incident is fully resolved. Thank you for your patience throughout this.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta Support System Unavailable
Affected: Kinsta support system
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our support system is not currently available. We are working to resolve the issue as quickly as possible.
-
identified
Our upstream provider has identified an issue and they are investigating into the matter as well. They have a status page open you may find at https://www.intercomstatus.com/us-hosting/incidents/01KEJ5AZFPGWKRV57MMEAR9M0W
-
identified
Intercom has identified a database issue and they are working on restoring the application as soon as possible. We appreciate your patience while the upstream provider works on resolving this issue.
-
monitoring
Intercom has implemented a fix and we are continuing to monitor the service.
-
resolved
Our support system is now available. We do apologize for any difficulties you experienced attempting to reach our support team.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta APM service disruption
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Engineers are investigating reports of performance issues with the APM data reported in MyKinsta. At this time APM data may not be displayed in MyKinsta. We are working to restore normal functionality to our APM system as quickly as possible. If you do have any questions...
-
investigating
We are continuing to investigate this issue and apologize for any inconvenience it may cause.
-
investigating
We are continuing to investigate this issue and apologize for any inconvenience it may cause.
-
investigating
We're still working on resolving this issue, and we sincerely apologize for any inconvenience it may have caused.
-
identified
We've identified the issue with our APM tool in MyKinsta. We are working on a fix for this.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Kinsta's status page.
MyKinsta actions are failing to complete.
Affected: MyKinsta
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
MyKinsta actions, such as adding domains, updating redirects, etc. are failing to complete. We are currently investigating the issue.
-
investigating
The MyKinsta dashboard is currently experiencing timeouts, which is causing some pages fail to load and certain actions failing to complete. We are actively investigating this issue and apologize for any inconvenience this may have caused.
-
identified
The issue has been identified, and a fix is being implemented.
-
identified
We are continuing to work on a fix to resolve this issue.
-
monitoring
A fix has been implemented, and we are monitoring the results.
-
resolved
This incident has been resolved. If you continue to experience similar issues, please contact our Support team via chat or email at support@kinsta.com.
Excerpts are shortened. Read the full incident on Kinsta's status page.