Production service lost outbound connectivity after redeploy
story-boards-ai
PROOP

4 hours ago

Our production Railway service ciaro-backend appears unable to make outbound connections.

From inside the running production container:

  • TCP connection to external Postgres times out: host: 13.57.136.47 port: 5432 error: connect ETIMEDOUT 13.57.136.47:5432
  • HTTPS fetch to Stytch fails: URL: https://api.stytch.com error: TypeError: fetch failed Redeploy/restart did not resolve it. After redeploy, startup still fails with: [Nest] ERROR [TypeOrmModule] Unable to connect to the database. Retrying (1)... Error: connect ETIMEDOUT 13.57.136.47:5432 Railway internal networking still works: the same service connects successfully to Redis via: redis://redis-tleo-prod.railway.internal:6379 This looks like outbound/external networking from the production runtime is broken, or the service is being routed through an egress path that external services reject/block. Project: Ciaro Pro Environment: production Service: ciaro-backend Can you check outbound egress/networking for this production service/runtime?

3 Replies

4 hours ago

most likely related to:


story-boards-ai
PROOP

4 hours ago

okay. switched that off. also switched regions. it recovered.

thats the second time we had issues in US West. Staying in US East for now


4 hours ago

I don't think it's related to us-west, more so just static ips in general


Welcome!

Sign in to your Railway account to join the conversation.

Loading...