We have identified the issue and pushed a fix. All services are back in a stable state.

Root cause: an internal routing configuration was mistakenly rolled back during an internal upgrade. This has been corrected and the endpoint is fully operational again.

We’re adding safeguards to prevent this from happening in the future.

Wallet History API is currently experiencing an increased number of errors on multiple chains. Our team is working on a fix.