We applied a hotfix for this issue 2.5 hours ago, at about 12:45 p.m. PDT today. We’ll continue to keep an eye on it. Thanks for the reports!