8bccf693-4059-4ef3-9dd0-55493979fdb7

you are getting timeouts when trying to connect to supabase from the railway service?

yeah and the open telemetry container that I have to relay the log too, I can't even connect to that (it's on the same railway network)

this happens on both staging and production env

so I tried to restart both container on staging, not any better

is this issue you are facing isolated to one single service? as in only one of your services seems like its cut off from the internet?

yeah I guess, but this happened at the same time for both staging and production

so maybe not just one

did you push some kind of an update during this time?

nope

7 day since last update

seems like it's back !

i saw that

why delete

I have redeployed 1 container and fixed

I'm gonna do the same on production

restart did not the trick but redeploy did

weird

makes sense

I can confirm, it's back and working ! Not sure why this happened and/or why redeploying fixed it

happy its back working for you