- Level
- confirmed
- Worst impact
- Degraded
- Components
- Logs
- Down Index
- 19of 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 2h 6m it lasted.
Anything that failed between 2026-03-13 15:25 UTC and 2026-03-13 17:31 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 5
- investigating
We're investigating an issue causing logs not to load.
provider
- identified
We've confirmed logs are loading with elevated delay. Our team is aware and working on a fix.
provider
- monitoring
We implemented a fix and are currently monitoring the result.
provider
- identified
We're seeing continued degradation on logs loading time. We are continuing to work on a fix.
provider
- resolved
This incident has been resolved.
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-fecd974917
Is Railway still down?
No, this incident was resolved 2026-03-13 17:31 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
2h 6m, from 2026-03-13 15:25 UTC to 2026-03-13 17:31 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.