5 months ago
Hi everyone,
We’ve been experiencing quite a bit of latency from the Amsterdam region — around 250 ms even for a simple /health check.
Is this expected on the Hobby plan, or could there be something else going on (routing, cold starts, regional load, etc.)?
Would love to know if others are seeing similar performance or if there are recommended optimizations. Thanks!
10 Replies
5 months ago
same
5 months ago
Same problem. Very frustrating...
5 months ago
Hi, can you run this and share the results here please? https://docs.railway.com/reference/network-diagnostics
Status changed to Awaiting User Response Railway • 5 months ago
nico
Hi, can you run this and share the results here please? <https://docs.railway.com/reference/network-diagnostics>
5 months ago
here
Attachments
Status changed to Awaiting Railway Response Railway • 5 months ago
nico
Hi, can you run this and share the results here please? <https://docs.railway.com/reference/network-diagnostics>
5 months ago
there you go!
Railway Network Diagnostics
Generated : Thursday, Feb 5 2026 10:47:03 WET
Endpoint : routing-info-production.up.railway.app
-------------------------------------------------------------------------------
Client IP Info
-------------------------------------------------------------------------------
{
"ip": "85.62.161.134",
"hostname": "emea.spain.8347.ip7.regusnet.com",
"city": "Madrid",
"region": "Madrid",
"country": "ES",
"loc": "40.4165,-3.7026",
"org": "AS12479 Orange Espagne SA",
"postal": "28004",
"timezone": "Europe/Madrid",
"readme": "https://ipinfo.io/missingauth"
}
-------------------------------------------------------------------------------
HTTP HEAD request
-------------------------------------------------------------------------------
Status: 200 OK
Status Code: 200
Protocol: HTTP/2.0
Response Headers:
X-Railway-Request-Id: LTZUAIP5Som7PJtWss7a6g
Content-Type: text/html
Date: Thu, 05 Feb 2026 10:47:04 GMT
Server: railway-edge
X-Railway-Edge: railway/europe-west4-drams3a
-------------------------------------------------------------------------------
DNS lookup (using system DNS)
-------------------------------------------------------------------------------
; <<>> DiG 9.10.6 <<>> routing-info-production.up.railway.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61314
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;routing-info-production.up.railway.app. IN A
;; ANSWER SECTION:
routing-info-production.up.railway.app. 60 IN A 66.33.22.232
;; Query time: 65 msec
;; SERVER: 85.62.161.130#53(85.62.161.130)
;; WHEN: Thu Feb 05 10:47:04 WET 2026
;; MSG SIZE rcvd: 83
-------------------------------------------------------------------------------
DNS lookup (using Cloudflare)
-------------------------------------------------------------------------------
; <<>> DiG 9.10.6 <<>> @1.1.1.1 routing-info-production.up.railway.app
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10183
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;routing-info-production.up.railway.app. IN A
;; ANSWER SECTION:
routing-info-production.up.railway.app. 60 IN A 66.33.22.232
;; Query time: 70 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Feb 05 10:47:04 WET 2026
;; MSG SIZE rcvd: 83
-------------------------------------------------------------------------------
Traceroute
-------------------------------------------------------------------------------
1 192.168.12.1 (192.168.12.1) 6.239 ms 3.225 ms
2 emea.spain.8347.ip2.regusnet.com (85.62.161.129) 4.347 ms 4.259 ms
3 100.66.191.33 (100.66.191.33) 7.554 ms 6.859 ms
4 10.34.193.30 (10.34.193.30) 8.785 ms 10.405 ms
5 10.34.193.1 (10.34.193.1) 32.376 ms 32.149 ms
6 10.34.35.2 (10.34.35.2) 32.310 ms 32.019 ms
7 10.34.206.61 (10.34.206.61) 42.120 ms 44.609 ms
8 193.251.249.1 (193.251.249.1) 32.328 ms 32.208 ms
9 193.251.150.76 (193.251.150.76) 35.260 ms 35.257 ms
10 prs-bb2-link.ip.twelve99.net (62.115.123.220) 67.379 ms 67.931 ms
11 adm-bb2-link.ip.twelve99.net (62.115.137.4) 66.863 ms 67.367 ms
12 adm-b12-link.ip.twelve99.net (62.115.137.191) 65.528 ms 65.612 ms
13 railwaycorp-ic-390073.ip.twelve99-cust.net (62.115.196.223) 64.849 ms 64.063 ms
14 66.33.22.232 (66.33.22.232) 71.376 ms 67.321 ms
-------------------------------------------------------------------------------
Ping (n=10)
-------------------------------------------------------------------------------
PING routing-info-production.up.railway.app (66.33.22.232): 56 data bytes
64 bytes from 66.33.22.232: icmp_seq=0 ttl=50 time=67.677 ms
64 bytes from 66.33.22.232: icmp_seq=1 ttl=50 time=67.650 ms
64 bytes from 66.33.22.232: icmp_seq=2 ttl=50 time=68.394 ms
64 bytes from 66.33.22.232: icmp_seq=3 ttl=50 time=71.711 ms
64 bytes from 66.33.22.232: icmp_seq=4 ttl=50 time=68.184 ms
64 bytes from 66.33.22.232: icmp_seq=5 ttl=50 time=69.421 ms
64 bytes from 66.33.22.232: icmp_seq=6 ttl=50 time=68.156 ms
64 bytes from 66.33.22.232: icmp_seq=7 ttl=50 time=68.196 ms
64 bytes from 66.33.22.232: icmp_seq=8 ttl=50 time=70.987 ms
64 bytes from 66.33.22.232: icmp_seq=9 ttl=50 time=67.721 ms
--- routing-info-production.up.railway.app ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 67.650/68.810/71.711/1.368 ms
Completed
lightshire
here
5 months ago
not seeing huge latency here especially for the region you're hitting. could you open a new thread with these results and a link to your service?
Status changed to Awaiting User Response Railway • 5 months ago
carlos-worfac
there you go! Railway Network Diagnostics Generated : Thursday, Feb 5 2026 10:47:03 WET Endpoint : [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app) \------------------------------------------------------------------------------- Client IP Info \------------------------------------------------------------------------------- { "ip": "85.62.161.134", "hostname": "[emea.spain.8347.ip7.regusnet.com](http://emea.spain.8347.ip7.regusnet.com)", "city": "Madrid", "region": "Madrid", "country": "ES", "loc": "40.4165,-3.7026", "org": "AS12479 Orange Espagne SA", "postal": "28004", "timezone": "Europe/Madrid", "readme": "<https://ipinfo.io/missingauth>" } \------------------------------------------------------------------------------- HTTP HEAD request \------------------------------------------------------------------------------- Status: 200 OK Status Code: 200 Protocol: HTTP/2.0 Response Headers: X-Railway-Request-Id: LTZUAIP5Som7PJtWss7a6g Content-Type: text/html Date: Thu, 05 Feb 2026 10:47:04 GMT Server: railway-edge X-Railway-Edge: railway/europe-west4-drams3a \------------------------------------------------------------------------------- DNS lookup (using system DNS) \------------------------------------------------------------------------------- ; <<>> DiG 9.10.6 <<>> [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61314 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;[routing-info-production.up.railway.app](http://routing-info-production.up.railway.app). IN A ;; ANSWER SECTION: [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app). 60 IN A 66.33.22.232 ;; Query time: 65 msec ;; SERVER: 85.62.161.130#53(85.62.161.130) ;; WHEN: Thu Feb 05 10:47:04 WET 2026 ;; MSG SIZE rcvd: 83 \------------------------------------------------------------------------------- DNS lookup (using Cloudflare) \------------------------------------------------------------------------------- ; <<>> DiG 9.10.6 <<>> @1.1.1.1 [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app) ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10183 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;[routing-info-production.up.railway.app](http://routing-info-production.up.railway.app). IN A ;; ANSWER SECTION: [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app). 60 IN A 66.33.22.232 ;; Query time: 70 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Thu Feb 05 10:47:04 WET 2026 ;; MSG SIZE rcvd: 83 \------------------------------------------------------------------------------- Traceroute \------------------------------------------------------------------------------- 1 192.168.12.1 (192.168.12.1) 6.239 ms 3.225 ms 2 [emea.spain.8347.ip2.regusnet.com](http://emea.spain.8347.ip2.regusnet.com) (85.62.161.129) 4.347 ms 4.259 ms 3 100.66.191.33 (100.66.191.33) 7.554 ms 6.859 ms 4 10.34.193.30 (10.34.193.30) 8.785 ms 10.405 ms 5 10.34.193.1 (10.34.193.1) 32.376 ms 32.149 ms 6 10.34.35.2 (10.34.35.2) 32.310 ms 32.019 ms 7 10.34.206.61 (10.34.206.61) 42.120 ms 44.609 ms 8 193.251.249.1 (193.251.249.1) 32.328 ms 32.208 ms 9 193.251.150.76 (193.251.150.76) 35.260 ms 35.257 ms 10 [prs-bb2-link.ip.twelve99.net](http://prs-bb2-link.ip.twelve99.net) (62.115.123.220) 67.379 ms 67.931 ms 11 [adm-bb2-link.ip.twelve99.net](http://adm-bb2-link.ip.twelve99.net) (62.115.137.4) 66.863 ms 67.367 ms 12 [adm-b12-link.ip.twelve99.net](http://adm-b12-link.ip.twelve99.net) (62.115.137.191) 65.528 ms 65.612 ms 13 [railwaycorp-ic-390073.ip.twelve99-cust.net](http://railwaycorp-ic-390073.ip.twelve99-cust.net) (62.115.196.223) 64.849 ms 64.063 ms 14 66.33.22.232 (66.33.22.232) 71.376 ms 67.321 ms \------------------------------------------------------------------------------- Ping (n=10) \------------------------------------------------------------------------------- PING [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app) (66.33.22.232): 56 data bytes 64 bytes from 66.33.22.232: icmp\_seq=0 ttl=50 time=67.677 ms 64 bytes from 66.33.22.232: icmp\_seq=1 ttl=50 time=67.650 ms 64 bytes from 66.33.22.232: icmp\_seq=2 ttl=50 time=68.394 ms 64 bytes from 66.33.22.232: icmp\_seq=3 ttl=50 time=71.711 ms 64 bytes from 66.33.22.232: icmp\_seq=4 ttl=50 time=68.184 ms 64 bytes from 66.33.22.232: icmp\_seq=5 ttl=50 time=69.421 ms 64 bytes from 66.33.22.232: icmp\_seq=6 ttl=50 time=68.156 ms 64 bytes from 66.33.22.232: icmp\_seq=7 ttl=50 time=68.196 ms 64 bytes from 66.33.22.232: icmp\_seq=8 ttl=50 time=70.987 ms 64 bytes from 66.33.22.232: icmp\_seq=9 ttl=50 time=67.721 ms \--- [routing-info-production.up.railway.app](http://routing-info-production.up.railway.app) ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 67.650/68.810/71.711/1.368 ms Completed
5 months ago
similarly not seeing any abnormal latency on our end, the 50~60ms comes from transit to railway from your isp/internet exchanges. could you open a new thread with these results and your service?
nico
similarly not seeing any abnormal latency on our end, the 50\~60ms comes from transit _to_ railway from your isp/internet exchanges. could you open a new thread with these results and your service?
5 months ago
which kind of metrics would you like me to provide?
Status changed to Awaiting Railway Response Railway • 5 months ago
5 months ago
I think it's related to this:
https://station.railway.com/questions/slow-requests-0cedf8d6
It's also regarding database operations and the ams region.
5 months ago
If y'all can make your own threads that'd be appreciated! Best way to track them all
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 5 months ago