Kinsta incident

Domain verification delays

Notice Resolved View vendor source →

Kinsta experienced a notice incident on September 13, 2025 affecting Cloudflare Integration, lasting 1d 21h. The incident has been resolved; the full update timeline is below.

Started
Sep 13, 2025, 04:30 AM UTC
Resolved
Sep 15, 2025, 02:21 AM UTC
Duration
1d 21h
Detected by Pingoru
Sep 13, 2025, 04:30 AM UTC

Affected components

Cloudflare Integration

Update timeline

  1. investigating Sep 13, 2025, 04:30 AM UTC

    Our Engineers are aware of reports of domain verification delays. This includes actions verifying new domains in MyKinsta. This appears to be related to a Cloudflare Custom Hostnames API endpoint issue that is currently ongoing. Cloudflare's own status page can be found at https://www.cloudflarestatus.com/incidents/k8fchbj6gcs4. We will continue to provide updates as they become available. If you do have any questions please do not hesitate to reach out to our Support team for assistance.

  2. investigating Sep 13, 2025, 04:59 PM UTC

    Cloudflare is continuing to investigate into the cause of this delay. We will continue to provide additional updates as more information becomes available. If you do have any questions please do not hesitate to reach out to our Support team for assistance.

  3. investigating Sep 14, 2025, 12:26 AM UTC

    Cloudflare is continuing their investigation into the cause of the custom hostname API delay. We will continue to provide additional updates as more information becomes available. If you do have any questions please do not hesitate to reach out to our Support team for assistance.

  4. investigating Sep 14, 2025, 04:41 PM UTC

    Cloudflare's investigation into the cause of the custom hostname API delay is continuing. We will continue to provide additional updates as more information becomes available. If you do have any questions please do not hesitate to reach out to our Support team for assistance.

  5. identified Sep 14, 2025, 09:40 PM UTC

    Cloudflare has identified the cause of the issue and is implementing a solution. We will continue to provide additional updates as more information becomes available. If you do have any questions please do not hesitate to reach out to our Support team for assistance.

  6. resolved Sep 15, 2025, 02:21 AM UTC

    This incident has been resolved.