- Level
- confirmed
- Worst impact
- Degraded
- Components
- Package Registry - npm
- Down Index
- 17of 100
What to do
Check whether you use Railway Package Registry - npm. 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 56m it lasted.
Anything that failed between 2026-01-29 20:08 UTC and 2026-01-29 21:04 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
They are currently investigating this issue.
provider
- monitoring
NPM Implemented a fix and is monitoring results.
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-d6900bbb7a
Is Railway still down?
No, this incident was resolved 2026-01-29 21:04 UTC. For Railway's live state, see https://down.guide/railway.
How long did it last?
56m, from 2026-01-29 20:08 UTC to 2026-01-29 21:04 UTC, by the times Railway posted.
What was affected?
Railway named Package Registry - npm.
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.