3 months ago
I have a Next.js service on Railway that had been deployed and running normally for over 10 hours. At around 04:30 UTC in March 2026, it suddenly started returning 502 errors. The issue lasted for about 2 minutes. Two related request IDs are "aUhFrr3oS_q3HjwV2prcFg" and "eGMRj8LVQPWVkLXeV7rehQ". Could someone help confirm whether this was more likely caused by a Railway networking issue or by the service itself?
3 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
2 months ago
My app was unresponsive for four minutes at exactly this time on March 7.
2 months ago
Maybe somewhat less than four minutes (my return to normalcy update said 4:03). But it has to have been a Railway issue but no notice. I have an extremely hard time with these unacknowledged issues no matter how short.
Times are in PT, pre-daylight saving time, so 4:30 UTC.
Attachments
2 months ago
This was a platform-side networking issue, not caused by either of your services. Application logs show no errors, crashes, or restarts during that window, and there were no deployments around that time. We're tracking this as a known issue and actively working on fixes. We hear the frustration about the lack of a public notice, and we appreciate you flagging it.
Status changed to Awaiting User Response Railway • 2 months ago
2 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 • 2 months ago