Skip to main content
Railway

Private Networking Degraded in Southeast Asia (Singapore)

Partial outage Lasted 1h 34m · started · Railway's page

Level
confirmed
Worst impact
Partial outage
Components
Traffic, Southeast Asia (Singapore)
Regions
apac

What to do

  • Check whether you use Railway Traffic, 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 1h 34m it lasted.

    Anything that failed between 2026-06-05 16:17 UTC and 2026-06-05 17: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 4

  1. investigating

    We are investigating an issue with private networking in our Southeast Asia (Singapore) region. Some workloads in this region may experience intermittent request timeouts when reaching their services. We are actively investigating the root cause and will provide updates as we learn more.

    provider

  2. identified

    We have identified that the issue involves degraded transit connectivity between our Southeast Asia (Singapore) region and our US East infrastructure. Some workloads experiencing cross-region connectivity may see intermittent request timeouts as a result. We are actively investigating the affected transit paths and working to restore normal connectivity. We will provide further updates as we make progress.

    provider

  3. monitoring

    We have identified a degraded transit path between our Southeast Asia (Singapore) region and our US East infrastructure as the root cause of the connectivity issues. We removed the affected transit provider and observed significant recovery in our network metrics. We are continuing to monitor the situation and investigating any remaining connectivity issues. We will provide a further update shortly.

    provider

  4. resolved

    The connectivity issues affecting private networking between our Southeast Asia (Singapore) region and US East infrastructure have been resolved. We identified a degraded transit path as the root cause and removed the affected transit provider, which restored normal connectivity. We apologize for any inconvenience caused. If you continue to experience issues, please contact support at https://station.railway.com.

    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-b8860cc910

Is Railway still down?

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

How long did it last?

1h 34m, from 2026-06-05 16:17 UTC to 2026-06-05 17:51 UTC, by the times Railway posted.

What was affected?

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