Kinsta incident

Cloudflare 500 error

Major Resolved View vendor source →

Kinsta experienced a major incident on August 12, 2025, lasting 8h 24m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2025, 01:33 PM UTC
Resolved
Aug 12, 2025, 09:57 PM UTC
Duration
8h 24m
Detected by Pingoru
Aug 12, 2025, 01:33 PM UTC

Update timeline

  1. identified Aug 12, 2025, 12:00 PM UTC

    There have been reports of 500 Cloudflare error, on websites using their own personal Cloudlare account and using APO service. Cloudflare has identified the issue: https://www.cloudflarestatus.com/incidents/vqq87ynv47rg and they are working on a fix.

  2. identified Aug 12, 2025, 12:06 PM UTC

    Update: Disabling the proxy settings in your personal Cloudflare DNS account, should help bring website up, until Cloudflare resolves the issue. https://www.cloudflarestatus.com/incidents/vqq87ynv47rg

  3. identified Aug 12, 2025, 01:33 PM UTC

    Cloudflare is still working on a permanent resolution: https://www.cloudflarestatus.com/incidents/vqq87ynv47rg If you are still experiencing issues, please try setting the Proxy status in your Cloudflare dashboard to "DNS only" instead of "Proxied", as that should resolve the error until Cloudflare resolves the issue.

  4. identified Aug 12, 2025, 02:35 PM UTC

    We are continuing to monitor the situation and will provide further updates as they become available from Cloudflare. If you are still experiencing issues, please try setting the Proxy status in your Cloudflare dashboard to "DNS only" instead of "Proxied", as that should resolve the error until Cloudflare resolves the issue.

  5. resolved Aug 12, 2025, 09:57 PM UTC

    Cloudflare has noted that this is resolved now: https://www.cloudflarestatus.com/incidents/vqq87ynv47rg If you do notice any other issues, please contact our support team.