same here. my services are in SouthEast Asia and getting 502 error

same here

I think we're having the same networking problem here on the Southeast Asia region. Just with the service we redeployed to this morning. Requests that don't hit the database seem to be okay (static files), so I suspect there's a networking problem between our application container and Postgres.

I think something is wrong with postgres

mongodb has no problem

fba556c2-09ab-4c36-a616-d5da0d54f6d6/service/a1f2748c-b3dd-4583-b150-e59142f62b91?environmentId=2c15a52c-7afd-4f3c-85fe-6525a58626d7

/project/b022b1af-4898-4f67-ae21-c86111a2e4b7/service/35f8e4c4-c40d-4bb3-ae98-f7b0e41c6999?environmentId=421d5a68-925f-4f65-9ff0-9b614e719486

It started working on my dev env when I migrated my dev postgres to US West

Please provide direct links to the service in question, this can be copied from your browser's omni bar while you have the service in question open.

fba556c2-09ab-4c36-a616-d5da0d54f6d6/service/a1f2748c-b3dd-4583-b150-e59142f62b91?environmentId=2c15a52c-7afd-4f3c-85fe-6525a58626d7

Apologies. https://railway.com/project/b022b1af-4898-4f67-ae21-c86111a2e4b7/service/35f8e4c4-c40d-4bb3-ae98-f7b0e41c6999?environmentId=421d5a68-925f-4f65-9ff0-9b614e719486

Mine was originally returning triggering 502 for all database-related requests, and eventually changed to timing out and hitting Cloudflare's 100s response time limit instead.

https://railway.com/project/7f0209a5-ac0e-4bdf-bdb2-00088f9178d4?environmentId=481b4a53-3bba-4674-91e7-43de6a29e0ed

Postgres, backend and front end are all in Southeast Asia, and having 502 gateway error on cloudflare

Looks like an incident has now been logged for this: https://railway.instatus.com/cma4wxa8j00047yj7joi492tw

I found a workaround in my deployment. If i use the string stored in DATABASE_PUBLIC_URL instead of the string stored in DATABASE_URL as my database connection string for my frontend, my app loads and works fine.

Public networking appears to be fine for the backend on mine, the problem appears to be with the internal networking between services.

EDIT: I take that back. Did another build and broke it :(

Please follow along with the incident linked above, we are actively working on a fix.

Hello All,

Update here, we have resolved the incident!

Again, very sorry for the inconvenience caused.