3 months ago
We are facing slow API responses on our Railway deployment. This is happening on multiple endpoints, including order create, order update, and print-time update.
Example logs:
[Nest] 20 - 06/03/2026, 5:09:25 PM WARN [HTTP] SLOW POST /orders 200 1382ms
[Nest] 20 - 06/03/2026, 5:15:47 PM WARN [HTTP] SLOW POST /orders 200 4650ms
[Nest] 20 - 06/03/2026, 5:24:24 PM WARN [HTTP] SLOW PATCH /orders/50ef4d0f-086a-472b-b9c0-a0ebf392ff70 200 1475ms
[Nest] 20 - 06/03/2026, 5:25:50 PM WARN [HTTP] SLOW PATCH /orders/3ffe1534-9b86-42f2-a957-ff1c131d861e 200 8138ms
[Nest] 20 - 06/03/2026, 5:30:39 PM WARN [HTTP] SLOW PATCH /orders/e2d7c583-74d0-4f3f-ae3e-e10bad774263/print-time 200 217327ms
[Nest] 20 - 06/03/2026, 5:33:56 PM WARN [HTTP] SLOW POST /orders 200 75033ms
[Nest] 20 - 06/03/2026, 5:35:41 PM WARN [HTTP] SLOW PATCH /orders/572585b8-6baf-4b3b-9d33-2cba312ce277 200 3937ms
[Nest] 20 - 06/03/2026, 5:38:17 PM WARN [HTTP] SLOW PATCH /orders/572585b8-6baf-4b3b-9d33-2cba312ce277/print-time 200 155330ms
[Nest] 20 - 06/03/2026, 5:44:11 PM WARN [HTTP] SLOW POST /orders 200 1735ms
[Nest] 20 - 06/03/2026, 5:51:07 PM WARN [HTTP] SLOW PATCH /orders/1a16e13f-c8c3-4aad-bd94-d8ccc72fe8bd 200 1141ms
[Nest] 20 - 06/03/2026, 5:51:44 PM WARN [HTTP] SLOW PATCH /orders/1a16e13f-c8c3-4aad-bd94-d8ccc72fe8bd 409 71524ms
[Nest] 20 - 06/03/2026, 5:59:58 PM WARN [HTTP] SLOW POST /orders 200 1301ms
The biggest delays are:
-
PATCH /orders/.../print-time took 217327ms
-
PATCH /orders/.../print-time took 155330ms
-
POST /orders took 75033ms
-
PATCH /orders/... returned 409 after 71524ms
-
NestJS backend
-
Railway PostgreSQL
-
Railway Redis / BullMQ
-
Prisma
-
Docker deployment
-
Node 20 slim image
This issue started yesterday, June 2, 2026. Before June 2, the same endpoints were
responding normally. The issue is not limited to
one endpoint. Even a simple print-time update is sometimes taking more than 2-3 minutes, so we suspect Railway-side database/
network/Redis latency, connection stalls, or resource throttling.
Can you please check for the timestamps above:
- PostgreSQL latency or lock waits
- Redis latency or connection stalls
- network/socket timeout issues
- service resource throttling
- deployment/container restarts
- any platform-side incidents
Screenshots/logs are attached.
Thanks.
Attachments
4 Replies
3 months ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 3 months ago
3 months ago
We are seeing intermittent slow POST requests on our NestJS/Node service hosted on Railway. We added detailed timing inside the app
to separate application processing from request body delivery.
Example affected request:
POST /orders 200 17133ms
requestId=1eb24f98-dec4-4525-b6ee-a60264fdd47a
headersSentMs=17132
firstTickLagMs=0.3
bodyFirstChunkMs=3798
bodyEndMs=17032
bodyBytes=304
contentLength=304
Application timing for the same request:
orders.create.complete totalMs=86
orders.controller.create.serviceDone serviceMs=86 sinceHttpStartMs=17132
in 5-34ms.
Based on Railway’s docs, public traffic is routed through Railway’s edge proxy before reaching the app. This looks like intermittent
request body delivery/proxy forwarding latency before our app logic runs, not a database or application processing
delay.
Could you please investigate the Railway edge/proxy/body forwarding path for this service around:
June 3, 2026, 7:53 PM UTC
Please also let us know which X-Railway-Edge and X-Railway-Request-Id values you need. We can reproduce and collect those headers
from the browser Network tab.
3 months ago
Hey, this might be part of the current incident that Railway has detected: https://status.railway.com/incident/4RCTTSB5.
In the meantime, can you go to https://{your domain}/.railway/cdn-trace and paste the output here? That will help us investigate the issue further.
passos
Hey, this might be part of the current incident that Railway has detected: https://status.railway.com/incident/4RCTTSB5. In the meantime, can you go to https://{your domain}/.railway/cdn-trace and paste the output here? That will help us investigate the issue further.
3 months ago
{"message":"Cannot GET /.railway/cdn-trace","error":"Not Found","statusCode":404}
chaudharyali14
{"message":"Cannot GET /.railway/cdn-trace","error":"Not Found","statusCode":404}
3 months ago
Is the issue still persisting?