Railway: Metrics and logs may be delayed or fail to load for some users

What to do

Check whether you use Railway Metrics, 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 41m it lasted.
Anything that failed between 2026-05-15 14:11 UTC and 2026-05-15 14:52 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.

investigatingMay 15, 2026, 2:11 PM UTC
We are currently investigating this incident
provider
identifiedMay 15, 2026, 2:22 PM UTC
We have identified the issue and are working towards a fix.
provider
monitoringMay 15, 2026, 2:38 PM UTC
We are seeing recovery and are monitoring the results. Metric and log request times should be at normal latency
provider
resolvedMay 15, 2026, 2:52 PM UTC
We have seen sustained recovery and normal latency. This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Railway still down?

No, this incident was resolved 2026-05-15 14:52 UTC. For Railway's live state, see https://down.guide/railway.

How long did it last?

41m, from 2026-05-15 14:11 UTC to 2026-05-15 14:52 UTC, by the times Railway posted.

What was affected?

Railway named Metrics, 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.