- Level
- confirmed
- Worst impact
- Degraded
- Components
- Dashboard - railway.com
- Down Index
- 20of 100
What to do
Check whether you use Railway Dashboard - railway.com. 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 3h 36m it lasted.
Anything that failed between 2026-06-02 16:15 UTC and 2026-06-02 19:51 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 3
- investigating
We are investigating reports of logs loading slowly or failing to load in the Railway dashboard. We are actively looking into the issue and will provide updates as we learn more.
provider
- monitoring
We have identified the cause of the slow log loading. Query latency has since recovered and we are continuing to monitor the situation. We will provide another update shortly.
provider
- resolved
We continue to monitor but logging is back to normal
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-5c5832d8ae
Is Railway still down?
No, this incident was resolved 2026-06-02 19:51 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
3h 36m, from 2026-06-02 16:15 UTC to 2026-06-02 19:51 UTC, by the times Railway posted.
What was affected?
Railway named Dashboard - railway.com.
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.