About two hours ago, we implemented a novel fix for the underlying issue here. We’ll continue to keep a close eye on this going forward, and we will take further action if necessary.