Skip to main content
Kinsta

Search and Replace bug when changing the primary domain in MyKinsta

Degraded Lasted 15d · started · Kinsta's page

Level
confirmed
Worst impact
Degraded
Components
MyKinsta
Down Index
23of 100

What to do

  • Check whether you use Kinsta MyKinsta. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 15d it lasted.

    Anything that failed between 2026-03-15 22:33 UTC and 2026-03-30 22:55 UTC may need a replay.
  • Subscribe to Kinsta's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=kinsta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Kinsta 26

  1. 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.

    provider

  2. investigating

    This bug has been reported to our MyKinsta development team. We will continue to provide updates as soon as it becomes available.

    provider

  3. investigating

    We are still investigating the issue.

    provider

  4. investigating

    We are continuing to investigate this issue.

    provider

  5. identified

    We have identified the issue and are actively working on implementing a fix.

    provider

  6. identified

    We are continuing to work on a fix for this issue.

    provider

  7. identified

    We are continuing to work on a fix for this issue.

    provider

  8. identified

    We are actively working on a solution to this issue.

    provider

  9. identified

    We are actively working on a solution to this issue.

    provider

  10. identified

    We continue to actively work on a solution to this issue.

    provider

  11. identified

    We continue to actively work on a solution to this issue.

    provider

  12. identified

    We continue to actively work on a solution to this issue.

    provider

  13. identified

    We are continuing to work on the fix for this issue.

    provider

  14. identified

    We continue to actively work on a solution to this issue.

    provider

  15. identified

    We continue to actively work on a solution to this issue.

    provider

  16. identified

    We continue to actively work on a solution to this issue.

    provider

  17. identified

    We are continuing to work on a fix for this issue.

    provider

  18. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  19. monitoring

    We are continuing to monitor for any further issues.

    provider

  20. monitoring

    We are continuing to monitor for any further issues.

    provider

  21. monitoring

    We are continuing to monitor for any further issues.

    provider

  22. monitoring

    We are continuing to monitor for any further issues.

    provider

  23. monitoring

    We are continuing to monitor for any further issues.

    provider

  24. monitoring

    We are continuing to monitor for any further issues.

    provider

  25. monitoring

    We are continuing to monitor for any further issues.

    provider

  26. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-b794726e70

Is Kinsta still down?

No, this incident was resolved 2026-03-30 22:55 UTC. For Kinsta's live state, see https://down.guide/kinsta.

How long did it last?

15d, from 2026-03-15 22:33 UTC to 2026-03-30 22:55 UTC, by the times Kinsta posted.

What was affected?

Kinsta named MyKinsta.

What caused it?

Kinsta hasn't published a root cause. If it does, it shows here.

Where does this come from?

Kinsta's official status page, https://status.kinsta.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.