hosting
Kinsta: security status
Summary
Official status page (Oct 21-22): from Oct 21, Cloudflare rules and config changes mitigated attacks on all sites while fixes rolled out as each was validated (8.5, 8.3, 8.0, 7.4, 8.1, 8.2, 8.4); resolved at 08:26 UTC on Oct 22: "All sites are protected, the PHP security updates have been rolled out across the platform, and we have no evidence of any breaches". An Oct 23 blog post says PHP 7.4-8.5 were updated on live and staging environments, with fixes for older versions from Freexian. No fixed version numbers are given.
Customer action:
No PHP version change or extra patch is needed. Environments suspended as a precaution can be reactivated. PHP 8.1 and older are out of upstream support, so plan a move to a supported PHP in MyKinsta.
Source: https://status.kinsta.com/incidents/c0c6xl1ghpb2
Verified: 2026-10-26
Managed WordPress on Google Cloud, fronted by Cloudflare. The ASN shows Cloudflare or Google Cloud, so sites are recognised by a CNAME to kinsta.cloud (sitename.hosting.kinsta.cloud) or by Kinsta's response headers, which also pass through a customer's own Cloudflare zone. Kinsta's DNS service uses Route 53 name servers and cannot be told from AWS. Kinsta's application and static-site hosting are not covered by this entry.
How this tool recognises the provider
- CNAME
*.kinsta.cloud- Response headers (names)
x-kinsta-cacheki-originx-edge-location-klb