- Level
- confirmed
- Worst impact
- Degraded
- Components
- Southeast Asia (Singapore)
- Regions
- apac
What to do
Check whether you use Railway Southeast Asia (Singapore) in apac. 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 25m it lasted.
Anything that failed between 2026-05-04 19:41 UTC and 2026-05-04 20:06 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 aware of an issue affecting edge routing in our Southeast Asia (Singapore) region. Users may experience failed requests or DNS resolution errors when reaching services deployed in this region. We are actively investigating and will provide updates as we learn more.
provider
- monitoring
Edge routing has recovered in Southeast Asia and we are monitoring the results.
provider
- resolved
We have seen consistent recovery and are marking this incident as 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-1154a3c054
Is Railway still down?
No, this incident was resolved 2026-05-04 20:06 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
25m, from 2026-05-04 19:41 UTC to 2026-05-04 20:06 UTC, by the times Railway posted.
What was affected?
Railway named Southeast Asia (Singapore) in apac.
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.