The deployment you referenced was replaced by a newer one that is running successfully. Two of your three service domains are serving 200 OK responses, but one has its target port hardcoded to 80 while your application is not listening there, causing "connection refused" errors on that domain. You can fix this by removing the port override on that domain in your service's networking settings, or setting it to the port your app actually binds to, and requests will route correctly.