Started: Mar 15, 10:33 PM
monitoring
We are continuing to monitor for any further issues.
Mar 30, 1:52 PM
monitoring
We are continuing to monitor for any further issues.
Mar 30, 3:26 AM
monitoring
We are continuing to monitor for any further issues.
Mar 29, 8:02 AM
monitoring
We are continuing to monitor for any further issues.
Mar 28, 6:40 AM
monitoring
We are continuing to monitor for any further issues.
Mar 27, 6:59 AM
monitoring
We are continuing to monitor for any further issues.
Mar 26, 2:29 PM
monitoring
We are continuing to monitor for any further issues.
Mar 26, 12:38 AM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 24, 12:34 PM
identified
We are continuing to work on a fix for this issue.
Mar 23, 2:50 PM
identified
We continue to actively work on a solution to this issue.
Mar 23, 3:29 AM
identified
We continue to actively work on a solution to this issue.
Mar 20, 2:04 PM
identified
We continue to actively work on a solution to this issue.
Mar 20, 1:22 AM
identified
We are continuing to work on the fix for this issue.
Mar 19, 2:13 PM
identified
We continue to actively work on a solution to this issue.
Mar 19, 8:06 AM
identified
We continue to actively work on a solution to this issue.
Mar 19, 3:09 AM
identified
We continue to actively work on a solution to this issue.
Mar 18, 2:05 PM
identified
We are actively working on a solution to this issue.
Mar 18, 7:15 AM
identified
We are actively working on a solution to this issue.
Mar 18, 2:30 AM
identified
We are continuing to work on a fix for this issue.
Mar 18, 1:21 AM
identified
We are continuing to work on a fix for this issue.
Mar 17, 2:09 PM
identified
We have identified the issue and are actively working on implementing a fix.
Mar 16, 11:54 PM
investigating
We are continuing to investigate this issue.
Mar 16, 2:22 PM
investigating
We are still investigating the issue.
Mar 16, 6:50 AM
investigating
This bug has been reported to our MyKinsta development team. We will continue to provide updates as soon as it becomes available.
Mar 16, 12:39 AM
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.
Mar 15, 10:33 PM