Resolved after 1 hour 29 minutes, affecting US East (Virginia, USA) (Deployments (US East)) and US West (California, USA) (Deployments (US West)) and 1 more, on July 15, 2025.
Our deployment pipeline throughput was impacted by a resource constraint on the database backing our Temporal cluster. We have increased cluster resources and upgraded the database; we have seen deployment throughput restored.
Affected components
Update timeline
- investigating Jul 15, 2025, 04:26 PM UTC
We are investigating a number of deploys that are stuck initializing. Non-Pro deployments have been temporarily paused.
- investigating Jul 15, 2025, 05:00 PM UTC
We continue to investigate the issue and have halted some active background operations to relieve the deployment delays
- identified Jul 15, 2025, 05:15 PM UTC
Deployments are now processing as we're reducing the queue backpressure. We have halted some background operations to relieve deployment delays.
- monitoring Jul 15, 2025, 05:42 PM UTC
Queue backpresssure has significantly reduced, we have re-enabled non-pro deployments and are monitoring
- resolved Jul 15, 2025, 05:55 PM UTC
Our deployment pipeline throughput was impacted by a resource constraint on the database backing our Temporal cluster. We have increased cluster resources and upgraded the database; we have seen deployment throughput restored.
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.
Amazon Web Services