The issue causing our main backend API to be unresponsive has been resolved, and the service is operating normally again.

We are currently investigating the root cause to understand why this occurred and to help prevent similar incidents in the future.

We apologize for the disruption and appreciate your patience.