Unfortunately the speculative fix we had for it didn't solve the issue as we'd hoped, but we're still working on getting it back up and running.