Search and Replace bug when changing the primary domain in MyKinsta

Summary

Search and Replace bug when changing the primary domain in MyKinsta

This incident has been resolved.

• Started

  Mar 15, 2026 · 10:33 PM

• Resolved

  Mar 30, 2026 · 10:55 PM

• Duration

  15d 22m

• Severity

  Minor

• ◐

  Investigating

  Mar 15 · 10:33 PM Kinsta

  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

  Mar 16 · 12:39 AM Kinsta

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

• ◐

  Investigating

  Mar 16 · 6:50 AM Kinsta

  We are still investigating the issue.

• ◐

  Investigating

  Mar 16 · 2:22 PM Kinsta

  We are continuing to investigate this issue.

• ◆

  Identified

  Mar 16 · 11:54 PM Kinsta

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

• ◆

  Identified

  Mar 17 · 2:09 PM Kinsta

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

• ◆

  Identified

  Mar 18 · 1:21 AM Kinsta

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

• ◆

  Identified

  Mar 18 · 2:30 AM Kinsta

  We are actively working on a solution to this issue.

• ◆

  Identified

  Mar 18 · 7:15 AM Kinsta

  We are actively working on a solution to this issue.

• ◆

  Identified

  Mar 18 · 2:05 PM Kinsta

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

• ◆

  Identified

  Mar 19 · 3:09 AM Kinsta

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

• ◆

  Identified

  Mar 19 · 8:06 AM Kinsta

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

• ◆

  Identified

  Mar 19 · 2:13 PM Kinsta

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

• ◆

  Identified

  Mar 20 · 1:22 AM Kinsta

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

• ◆

  Identified

  Mar 20 · 2:04 PM Kinsta

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

• ◆

  Identified

  Mar 23 · 3:29 AM Kinsta

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

• ◆

  Identified

  Mar 23 · 2:50 PM Kinsta

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

• ◉

  Monitoring

  Mar 24 · 12:34 PM Kinsta

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

• ◉

  Monitoring

  Mar 26 · 12:38 AM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 26 · 2:29 PM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 27 · 6:59 AM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 28 · 6:40 AM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 29 · 8:02 AM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 30 · 3:26 AM Kinsta

  We are continuing to monitor for any further issues.

• ◉

  Monitoring

  Mar 30 · 1:52 PM Kinsta

  We are continuing to monitor for any further issues.

• ✓

  Resolved

  Mar 30 · 10:55 PM Kinsta

  This incident has been resolved.