Railway incident

We are investigating issues with elevated network latency and slow deploys

Resolved after 1 day 11 hours, affecting US East (Virginia, USA) (Deployments (US East)) and US West (California, USA) (Deployments (US West)) and 1 more, on December 16, 2025.

investigating Dec 17, 2025, 07:04 PM UTC

A post-mortem of this incident has been published at .

Started: Dec 16, 2025, 07:10 AM UTC
Resolved: Dec 17, 2025, 07:04 PM UTC
Duration: 1d 11h
Detected by Pingoru: Dec 16, 2025, 07:10 AM 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

investigating Dec 16, 2025, 07:10 AM UTC

We are currently investigating this incident.
identified Dec 16, 2025, 07:37 AM UTC

We continue to see degradation across all regions, and are working on a fix. We have paused new deploys as we investigate.
monitoring Dec 16, 2025, 08:06 AM UTC

We are rolling out a fix and are seeing recovery in all regions. Deploys have been re-enabled
monitoring Dec 16, 2025, 08:30 AM UTC

We have seen recovery in all regions. We are continuing to monitor this incident.
monitoring Dec 16, 2025, 09:08 AM UTC

We are seeing further degradation, particularly in EU regions. We are continuing to work on a permanent fix.
monitoring Dec 16, 2025, 10:30 AM UTC

We are still monitoring this incident.
monitoring Dec 16, 2025, 11:00 AM UTC

We have seen widespread recovery and are continuing to monitor this incident.
resolved Dec 16, 2025, 11:20 AM UTC

This incident has been resolved.
investigating Dec 17, 2025, 07:04 PM UTC

A post-mortem of this incident has been published at .

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.