We experienced a major service disruption that was resolved at 07:57 UTC today. Your services were redeployed shortly after at around 08:11 UTC. The 502 errors are likely residual effects from this incident. Please try accessing your app again now, and if the issue persists, try redeploying your Frontend service from the project dashboard.

same here. Tried again, same 502

Your Frontend and Backend services were auto-redeployed at around 08:11 UTC after the major service disruption, and they show SUCCESS status, but we can see they are producing no runtime logs at all, which explains the 502 errors - the containers are not properly serving traffic. Your custom domains and certificates are healthy. Please trigger a fresh redeploy of both your Frontend and Backend services by clicking the three-dot menu on the latest deployment and selecting "Redeploy" to get fresh containers started properly.

Works after redeploy

Glad to hear it! The redeploy got everything back on track. If anything else comes up, feel free to reach out.