Railway incident

Deployments are slow to progress

Resolved after 55 minutes, affecting US East (Virginia, USA) (Deployments (US East)) and US West (California, USA) (Deployments (US West)) and 1 more, on August 18, 2026.

resolved Aug 18, 2026, 10:40 PM UTC

We have fixed the issue causing deployments to slow and they have returned to normal.

Started
Aug 18, 2026, 09:45 PM UTC
Resolved
Aug 18, 2026, 10:40 PM UTC
Duration
55m
Detected by Pingoru
Aug 18, 2026, 09:45 PM UTC

Affected components

US East (Virginia, USA) (Deployments (US East))US West (California, USA) (Deployments (US West))EU West (Amsterdam, Netherlands) (Deployments (EU West))Southeast Asia (Singapore) (Deployments (Southeast Asia))

Update timeline

  1. investigating Aug 18, 2026, 09:45 PM UTC

    We are aware of an issue causing deployments to remain in an initializing state longer than expected. Users may experience delays in new deployments progressing. We are actively investigating and will provide updates as we learn more.

  2. monitoring Aug 18, 2026, 10:17 PM UTC

    We have identified the root cause as an issue with our task queue processing, which is causing builds and deployments to progress more slowly than usual. A revert is currently in progress. Users may continue to experience delays in deployments progressing. We will provide another update once the fix is deployed.

  3. resolved Aug 18, 2026, 10:40 PM UTC

    We have fixed the issue causing deployments to slow and they have returned to normal.

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 →