The issue has been resolved, though it may take some time for the changes to fully propagate.

We’ve rolled back the change related to dropping invalid headers in the Load Balancer configuration, and we’re monitoring the situation closely.

We’ve identified the issue as being related to the Load Balancer settings, and our team is actively working on a resolution.

Error: "Invalid API request or invalid signature"