11 days ago
Even simple health checks are taking 1 second~ . Not sure if this is something that happens on the hobby plan? If yes, then kinda sucks that i'm being forced into paying higher without actually being able to properly evaluated the product.
here are my network diagnostics
Railway Network Diagnostics
Generated : Saturday, Feb 28 2026 16:25:37 CST
Endpoint : routing-info-production.up.railway.app
-------------------------------------------------------------------------------
Client IP Info
-------------------------------------------------------------------------------
{
"ip": "96.71.137.126",
"city": "Southaven",
"region": "Mississippi",
"country": "US",
"loc": "34.9890,-90.0126",
"org": "AS7922 Comcast Cable Communications, LLC",
"postal": "38671",
"timezone": "America/Chicago",
"readme": "https://ipinfo.io/missingauth"
}
-------------------------------------------------------------------------------
HTTP HEAD request
-------------------------------------------------------------------------------
Status: 200 OK
Status Code: 200
Protocol: HTTP/2.0
Response Headers:
X-Railway-Edge: railway/us-east4-eqdc4a
X-Railway-Request-Id: aL_8-yeYT8G3a6idwoOzXw
Accept-Ranges: bytes
Date: Sat, 28 Feb 2026 22:25:38 GMT
Via: 1.1 varnish
X-Railway-Cdn-Edge: fastly/cache-dfw-kdfw8210064-DFW
Server: railway-edge
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1772317539.758401,VS0,VE216
Content-Type: text/html
-------------------------------------------------------------------------------
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: 9576
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;routing-info-production.up.railway.app. IN A
;; ANSWER SECTION:
routing-info-production.up.railway.app. 58 IN A 151.101.2.15
;; Query time: 1091 msec
;; SERVER: 192.168.10.10#53(192.168.10.10)
;; WHEN: Sat Feb 28 16:25:40 CST 2026
;; MSG SIZE rcvd: 72
-------------------------------------------------------------------------------
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: 24843
;; 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 151.101.2.15
;; Query time: 90 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Feb 28 16:25:40 CST 2026
;; MSG SIZE rcvd: 83
-------------------------------------------------------------------------------
Traceroute
-------------------------------------------------------------------------------
1 dsr-250 (192.168.10.10) 6.325 ms 2.662 ms
2 docsis-gateway (10.1.10.1) 5.063 ms 4.941 ms
3 96.120.15.157 (96.120.15.157) 9.108 ms 10.673 ms
4 po-303-1216-rur02.hattiesburg.ms.malt.comcast.net (68.86.247.21) 12.065 ms 14.643 ms
5 po-2-rur01.hattiesburg.ms.malt.comcast.net (96.108.30.221) 11.089 ms 16.157 ms
6 be-55-ar01.hornlake.tn.malt.comcast.net (96.108.173.113) 30.138 ms 26.585 ms
7 162.151.119.229 (162.151.119.229) 31.321 ms 31.400 ms
8 be-34922-cs02.dallas.tx.ibone.comcast.net (68.86.95.117) 35.010 ms 1122.616 ms
9 be-3201-pe01.1950stemmons.tx.ibone.comcast.net (68.86.85.38) 48.005 ms 39.323 ms
10 * *
11 151.101.2.15 (151.101.2.15) 44.706 ms 36.762 ms
-------------------------------------------------------------------------------
Ping (n=10)
-------------------------------------------------------------------------------
PING routing-info-production.up.railway.app (151.101.2.15): 56 data bytes
64 bytes from 151.101.2.15: icmp_seq=0 ttl=55 time=37.869 ms
64 bytes from 151.101.2.15: icmp_seq=1 ttl=55 time=834.515 ms
64 bytes from 151.101.2.15: icmp_seq=2 ttl=55 time=40.273 ms
64 bytes from 151.101.2.15: icmp_seq=3 ttl=55 time=872.958 ms
64 bytes from 151.101.2.15: icmp_seq=4 ttl=55 time=44.000 ms
64 bytes from 151.101.2.15: icmp_seq=5 ttl=55 time=953.305 ms
64 bytes from 151.101.2.15: icmp_seq=6 ttl=55 time=47.022 ms
64 bytes from 151.101.2.15: icmp_seq=7 ttl=55 time=956.492 ms
64 bytes from 151.101.2.15: icmp_seq=8 ttl=55 time=33.766 ms
64 bytes from 151.101.2.15: icmp_seq=9 ttl=55 time=1004.201 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 = 33.766/482.440/1004.201/444.006 ms
Completed
1 Replies
Status changed to Awaiting Railway Response Railway • 11 days ago
10 days ago
Based on the diagnostics you posted, this does not appear to be a Railway performance issue.
Your ping results show very large jitter:
~40 ms → ~900 ms → ~40 ms → ~950 ms
If Railway were slow, latency would be consistently high. Instead the connection alternates between normal and extremely slow responses, which usually indicates network congestion between your ISP and the destination.
Your traceroute also shows a spike inside the Comcast backbone:
be-34922-cs02.dallas.tx.ibone.comcast.net
1122 ms
This suggests the delay is happening on the ISP routing path before reaching Railway's edge.
Another clue is the DNS lookup timing:
system DNS ≈ 1091 ms
Cloudflare DNS ≈ 90 ms
which indicates the local resolver is also slow.
You may want to test from another network or region (for example using a cloud VM or online latency tester) to confirm. The Hobby plan itself should not introduce a consistent 1s delay for simple health checks.