Thanks for bringing this to our attention! It looks like we had some issues with a deploy rollout that were not caught by our automated checks (going to be adding this to our automated checks in the future) - the issue should now be fixed and the node should be working properly in all cases again.