⏺ Now let me hit a few endpoints to check if it's up. ⏺ Bash(curl -s -o /dev/null -w "transport-type: HTTP %{http_code} (%{time_total}s)\n" "https://mayadev.mayaresearch.ai/api/v6/transport-type") ⎿ transport-type: HTTP 502 (0.285074s) ⏺ Bash(curl -s -o /dev/null -w "on_open: HTTP %{http_code} (%{time_total}s)\n" "https://mayadev.mayaresearch.ai/api/v6/on_open?device_id=test&timezone=Asia/Kolkata") ⎿ on_open: HTTP 502 (0.198947s) ⏺ Bash(curl -s -o /dev/null -w "personas: HTTP %{http_code} (%{time_total}s)\n" "https://mayadev.mayaresearch.ai/api/v6/personas?page=1&page_size=1®ion=IN") ⎿ personas: HTTP 502 (0.165434s) ⏺ Bash(curl -s -o /dev/null -w "check-limits: HTTP %{http_code} (%{time_total}s)\n" "https://mayadev.mayaresearch.ai/api/v6/check-limits?device_id=test&persona_id=test…) ⎿ check-limits: HTTP 502 (0.179492s) ⏺ All endpoints are returning 502 Bad Gateway. The prod server at https://mayadev.mayaresearch.ai is down — the reverse proxy (nginx/load balancer) is reachable but the backend service behind it isn't running or is crashed. This also explains the SSH connection refused error you pasted — the server at 216.81.248.184 port 22 is refusing connections, so the machine itself may be down or SSH service stopped. You'll need to get into the server to restart the backend service. Since SSH is also refused, you may need to use your cloud provider's console (e.g., DigitalOcean/AWS dashboard) to restart the instance or access it via web console. ✻ Crunched for 33s ─────────────────────────────────────────────────────────────────────────────────────────────── ❯ ─────────────────────────────────────────────────────────────────────────────────────────────── ⏵⏵ bypass permissions on (shift+tab to cycle)