I’m not seeing it here (west coast USA). The only way I could see Rule Machine being part of the problem is if your configuration has created a race condition, as described in the OP:
Caution: Rules that use multiple rule-truths as conditions can fail due to race conditions should those tied-to Rules change state simultaneously. Best practice would be to avoid using multiple rule-truth conditions in a single Rule. Triggers do not have this issue; multiple rule-truth events in a Trigger are treated such that any of the Rules proving true/false (as selected) causes the Trigger to take action.
If the above is not relevant to your situation, try opening a chat session with Support.