We applied a patch that resolves the issue. We have implemented additional tests to the area of the codebase to ensure this doesn't happen again.

A bug was introduced to our API client that caused issue signing in via satellite domains, and caused configurations proxying FAPI to revert back to un-proxied FAPI calls.