- Level
- confirmed
- Worst impact
- Major outage
- Components
- Dashboard - railway.com
- Down Index
- 40of 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 1h 5m it lasted.
Anything that failed between 2026-02-13 01:00 UTC and 2026-02-13 02:05 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 4
- investigating
We are currently investigating this incident. All running services are fully operational, only login is affected.
provider
- identified
A Redis shard on the Dashboard is timing out. A subset of users may see dashboard timeouts
provider
- monitoring
We implemented a fix and are currently monitoring the result. We're seeing recovery on queued deployments as well.
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-eb713bb987
Is Railway still down?
No, this incident was resolved 2026-02-13 02:05 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
1h 5m, from 2026-02-13 01:00 UTC to 2026-02-13 02:05 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.