Your backend's latest deployment is showing as failed, which is consistent with the ongoing service disruption that is now in the recovery/monitoring phase. Your MongoDB and Redis services have both recovered successfully. The incident update notes that some workloads still need a redeploy - please trigger a redeploy of your backend service from the dashboard or CLI, and private networking should resume normally once the new deployment is running.

thanks, I have been through the logs, so I know it failed... I also tried to redeploy it a few times, but the error points at the private network connectivity. So my question remains, are you 100% aware of what needs to be fixed on your end and this will "work again at some stage" or is that something you are not actually aware of. I understand this is a massive issue with loads of customers bomabrding you and I appreciate the quick response.

seems we need mongodb.railway.internal DNS resolution fixed within railways private network.

your incident wiped env settings. hope this helps someone else too. as per diagnostic logs.