This was resolved with this morning’s updates, but we’re still keeping an eye out – please let us know if it happens again!