Hi Railway team,

We're seeing intermittent latency spikes on our production service running in the Singapore region.

Symptoms

Most requests complete in around 95–100ms, but approximately 25% of requests suddenly take 2–8 seconds.

This occurs even on a lightweight health endpoint:

GET /api/health

There is no database query or heavy processing involved.

Reproduction

Running the following command repeatedly from Japan:

for i in $(seq 100); do
  curl -sS -o /dev/null \
    -w "%{time_total}\n" \
    --resolve buy-buy.pro:443:<SERVICE_IP> \
    https://buy-buy.pro/api/health
done

Typical output:

0.097
0.101
0.096
5.616
0.098
4.525
0.097
1.341
0.099
2.108
...

Observed distribution:

• Median: ~99ms
• About 25% of requests exceed 1 second
• Many requests take 4–8 seconds
• Maximum observed: ~8 seconds

The issue is reproducible across multiple runs.

Environment

• Region: Singapore
• Client location: Japan
• HTTPS
• Production service
• Using --resolve to bypass DNS, so DNS lookup is not part of the latency.

We've also noticed recent Singapore networking incidents on the Railway status page, so we're wondering if this could be related to the current edge or transit infrastructure.

Could you please investigate whether there are any known networking or routing issues affecting the Singapore region?

If needed, we're happy to provide:

• Project ID
• Service ID
• Exact timestamps (UTC)
• Public IP used for testing
• Additional latency logs

Thank you!