it's fetching from the backend service and using the public url and not the railway internal url

the backend service itself is not having any latency or downtime so this makes it clear that internal network is having this latency

Can you try using something like curl to make a fetch to the backend service in an already-running service via ssh?

sure

using postman, it's giving decent latency

but i did this from my pc

in an already-running service via ssh

and do you see this request in http logs on the backend service?

is it even possible to ssh inside any railway service?

Yes

whoa

right click on a service, "copy ssh command"

new feature unlocked dang

error: unrecognized subcommand 'ssh'

  tip: a similar subcommand exists: 'starship'

Usage: railway [OPTIONS] 

For more information, try '--help'.

??

What version are you on?

oh got it

updating

don't got curl installed in the service so hard

apt install -y curl

apk add curl if alpine

time_total: 2.511792s

yeah the latency is high

testing more endpoints

i mean it's not that bad when i do curl

really weird issue

It's working perfectly on my machine when i build the nextjs project

🫠

Okay so i got it!

Singapore region is having some issues for sure!

i changed my all services to EU and everything's working perfectly!