Railway incident

Single host on Railway Metal (us-west2) is offline

Resolved after 42 minutes, affecting US West (California, USA) (Deployments (US West)) and Southeast Asia (Singapore) (Deployments (Southeast Asia)), on May 4, 2025.

monitoring May 04, 2025, 10:01 PM UTC

All deployments on the offline host have successfully recovered.

Started
May 04, 2025, 09:33 PM UTC
Resolved
May 04, 2025, 10:15 PM UTC
Duration
42m
Detected by Pingoru
May 04, 2025, 09:33 PM UTC

Affected components

US West (California, USA) (Deployments (US West))Southeast Asia (Singapore) (Deployments (Southeast Asia))

Update timeline

  1. investigating May 04, 2025, 09:33 PM UTC

    We are currently investigating this incident. A small subset of impacted users on us-west2 region may notice their deployments are unresponsive during this period. You can re-deploy your service to mitigate this.

  2. identified May 04, 2025, 09:53 PM UTC

    We have identified an issue with the offline host, and confirmed that full recovery is in progress.

  3. monitoring May 04, 2025, 10:01 PM UTC

    All deployments on the offline host have successfully recovered.

  4. resolved May 04, 2025, 10:15 PM UTC

    This incident has been resolved.

Your product runs on more than Railway

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →