We have not made any changes. If our edge is returning a 503, it means your app is unresponsive. Given it's a Node app, and the vCPU usage is hovering around 1 vCPU, that checks out. You will want to horizontally scale out.

Issue happened after i pushed build at 2:54

I've stated the facts. I'll step out and defer this to the community because our side of things is operating normally.

alright thanks for the help

Is there detailed docs on the edge proxy behavior and config?

Your app doesn't respond consistently. We send a 503. I think your focus should be on why your app is consuming 1 vCPU, and if that's normal, then you need to horizontally scale.

same exact build redeployed today fixed all 503 issues. same cpu usage, same amount of network requests, no code change.