- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Logs
- Down Index
- 31of 100
What to do
Check whether you use Railway Logs. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 4h 22m it lasted.
Anything that failed between 2026-05-27 17:19 UTC and 2026-05-27 21:41 UTC may need a replay.Subscribe to Railway's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=railway works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Railway 7
- investigating
We are investigating an issue affecting build log delivery. Some build logs may be missing or incomplete for deployments since approximately 14:46 UTC. Your running applications are not affected, and historical logs from before this window remain available. We are actively investigating and will provide updates as we learn more.
provider
- monitoring
We have deployed a fix for the build log delivery issue and are now monitoring to confirm full recovery. Some build logs from the affected window (approximately 14:46–17:53 UTC) will be permanently missing. We will provide a further update once we have confirmed stability.
provider
- investigating
While monitoring, we continued to see periods where build logs may be missing or incomplete. The earlier fix addressed part of the underlying issue, but the problem has not been fully resolved. We are actively investigating. Your running applications are not affected. We will provide a further update as we learn more.
provider
- investigating
We are continuing to investigate the build log delivery issue. We are still seeing periods where build logs may be missing or incomplete, and have not yet reached a full resolution. Your running applications are not affected. We will provide a further update as we learn more.
provider
- identified
We have identified the cause of the build log delivery issue. We have deployed a fix to address this and are in the process of rolling it out across our build infrastructure. We are monitoring for recovery and will provide a further update once we have confirmed stability. Your running applications are not affected. Build logs from the affected window may be permanently missing.
provider
- monitoring
We have identified and resolved the underlying cause of the build log delivery issue. A fix has been deployed and we are now monitoring to confirm full recovery. Your running applications are not affected. Build logs from the affected window may be permanently missing. We will provide a further update once we have confirmed stability.
provider
- resolved
We have confirmed that the build log delivery issue has been resolved. Build logs are now being delivered successfully and metrics have returned to normal levels. We apologize for the disruption. Build logs from the affected window may be permanently missing. Your running applications were not affected at any point during this incident.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-23df3e3573
Is Railway still down?
No, this incident was resolved 2026-05-27 21:41 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
4h 22m, from 2026-05-27 17:19 UTC to 2026-05-27 21:41 UTC, by the times Railway posted.
What was affected?
Railway named Logs.
What caused it?
Railway hasn't published a root cause. If it does, it shows here.
Where does this come from?
Railway's official status page, https://status.railway.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.