Deployments are currently taking longer than usual to start, and some may stay queued for longer than expected. We are investigating and working to bring them back to normal speed.

Builds remain available for Pro and Enterprise workspaces. We are continuing to work on enabling builds for Hobby, then Free and Trial.

We will provide another update by 08:00 UTC at the latest.

Builds are now available for Pro and Enterprise workspaces. Pro customers can now complete the steps in our published guides that require a redeploy.

We will provide another update by 07:10 UTC at the latest.

Enterprise deployments are now moving through each stage at normal speed, including the "Running pre-deploy command" stage. Deployments that were waiting at one stage are continuing on their own, and no action is needed.

We will provide another update by 06:45 UTC, or sooner if there is news before then.

We are continuing to work on deployments that stay at one stage, such as "Running pre-deploy command", for longer than expected. There is no other change to report since our last update.

Builds remain available for Enterprise workspaces. We are continuing to work on enabling builds for Pro, Hobby, then Free and Trial.

We will provide another update by 06:45 UTC, or sooner if there is news before then.

Deployments are taking longer than usual to progress through each stage. Users may see a deployment stay at one status, such as "Running pre-deploy command", for longer than expected. We are investigating and working on a fix.

We will provide another update by 06:00 UTC at the latest.

The Redeploy feature has been fixed. Enterprise customers can now use the Redeploy feature.

We are continuing to work on enabling builds for all other tiers.

We will provide another update by 05:30 UTC at the latest.

Services with pre-deploy commands are stuck at the “Running pre-deploy command” stage. We are currently investigating and working on a fix.

We will provide another update by 05:15 UTC at the latest.

In accordance with our security disclosure, we have invalidated all Railway API tokens. If you are using an API token to integrate with Railway’s Public API (https://docs.railway.com/integrations/api), it will no longer work. Please create new API tokens on Railway to continue using Railway’s Public API.

We will provide another update by 05:00 UTC at the latest.

Builds for Enterprises continue to be available.

Please note that the Redeploy feature is currently unavailable. To initiate a redeploy, please browse to your service -> Ctrl/CMD+K -> Deploy Latest Commit. We are working to re-enable the Redeploy feature and will provide an update as soon as available.

We will provide another update by 04:45 UTC at the latest.

Builds for Enterprise workspaces are now available. Enterprise customers can now complete the steps in our published guides that require a redeploy, including applying any new credentials you have added in Railway.

Pro, Hobby, then Free and Trial will follow in stages. We will post here as each is enabled, and the guides remain the recommended next steps regardless of plan.

We will provide another update by 04:15 UTC or sooner.

Builds remain paused. We are continuing to work to bring them back online and expect to have an update for Enterprise users here soon.

The guides published earlier cover the steps you can begin taking now. We will provide another update by 03:45 UTC, or sooner if there is news before then.

We are still working to bring builds back online. There is no change to report since our last update.

The guides published in our previous update cover the recommended next steps regarding the security notice. Some of those steps require a redeploy and will have to wait until builds are available, but others you can begin now.

We will provide another update by 03:00 UTC, or sooner if builds are back before then.

We have published guides to help users through recommended next steps regarding the security notice. These guides may require redeployment of services which you will not be able to complete until Builds are available again. However, there are steps you may begin to take. We will update as soon as Builds are available. This page remains the fastest place for updates.

Published Guides:
- Check for Unexpected OpenRouter Usage: https://blog.railway.com/p/security-disclosure-recommendation-check-for-unexpected-openrouter-usage
- Rotate PostgreSQL Database Credentials: https://blog.railway.com/p/security-disclosure-recommendation-rotate-postgresql-database-credentials
- Check for Unexpected Grok Usage: https://blog.railway.com/p/security-disclosure-recommendation-check-for-unexpected-grok-usage
- Redeploy Buckets and Reconnect GitHub After the Credential Reset: https://blog.railway.com/p/security-disclosure-recommendation-redeploy-buckets-and-reconnect-github-after-the-credential-reset
- Check for Unexpected Anthropic Usage: https://blog.railway.com/p/security-disclosure-recommendation-check-for-unexpected-anthropic-usage
- Check for Unexpected OpenAI Usage: https://blog.railway.com/p/security-disclosure-recommendation-check-for-unexpected-openai-usage
- Check for Unexpected Usage in Stripe: https://blog.railway.com/p/security-disclosure-recommendation-check-for-unexpected-usage-in-stripe
- Check for Anomalous GitHub Access: https://blog.railway.com/p/security-disclosure-recommendation-check-for-anomalous-github-access
- Rotate MongoDB Database Credentials: https://blog.railway.com/p/security-disclosure-recommendation-rotate-mongodb-database-credentials
- Rotate Redis Database Credentials: https://blog.railway.com/p/security-disclosure-recommendation-rotate-redis-database-credentials
- Rotate MySQL Database Credentials: https://blog.railway.com/p/security-disclosure-recommendation-rotate-mysql-database-credentials
- Check for Anomalous AWS Access: https://blog.railway.com/p/security-disclosure-recommendation-check-for-anomalous-aws-access
- Check for Anomalous GCP Access: https://blog.railway.com/p/security-disclosure-recommendation-check-for-anomalous-gcp-access

We are continuing to work to make builds available again. We will be publishing guides shortly to help users through recommended next steps regarding the security notice. This page remains the fastest place for updates.

Please note that customers may see revocation of storage bucket credentials performed by Railway employee "Faraz Patankar" in their audit logs or activity panel. This is expected, as we previously indicated, we are revoking all existing storage bucket credentials out of an abundance of caution.

We are continuing to rotate bucket credentials and are working to make builds available again as soon as possible. We do not have further details to share right now, and this page remains the fastest place for updates as we learn more.

If you need to reach us, you can email [email protected]. Please note that we may not be able to share more detail than is published here.

Builds remain paused. We will post here as soon as they resume.

We are rotating all Railway bucket credentials in response to the security incident. New credentials will appear in your dashboard automatically.

Because deployments are paused, you will not be able to redeploy your services to pick up the new credentials until builds are restored. We will post here when builds resume with any additional details.

We have published a security notice covering what we know so far and the actions we recommend you take: https://blog.railway.com/p/security-disclosure-wednesday-october-21st

We strongly recommend that you revoke all environment variables stored in Railway, including API keys and private registry credentials, and review your service logs for unusual activity.

Deployments remain paused while we investigate, including for Enterprise customers. We understand you are unable to update your applications with new credentials at this time and sincerely apologize for the inconvenience. We will post here when builds are restored.

As we confirm which accounts were affected, we will contact those customers directly by email.

We do not yet have additional information to provide about the availability of builds. We apologize for the inconvenience and we will provide an update as soon as we can.

We are validating builds for Enterprise workspaces and should be re-enabling for Enterprises broadly very soon. Pro, Hobby, then Free and Trial will follow in stages, and we will post here as each is enabled.

Some users will be signed out and will need to log in again.

We will continue posting updates at least every 30 minutes, and sooner if we have more information. The next update will by 21:00 UTC.

We are continuing to work towards enabling builds for Enterprise workspaces.

We will continue posting updates at least every 30 minutes, and sooner if we have more information. The next update will be at 21:00 UTC latest.

We are continuing to work on a fix for build issues. Due to impact from adjacent cache systems, we are invalidating OAuth sessions as part of our mitigation. Affected users will be signed out and will need to log in again.

We continue to expect builds for Enterprise workspaces to be available by 20:30 UTC. It is possible that this could be delayed by up to 30 minutes, but we will provide an update at 20:30 UTC regardless. Pro, Hobby, then Free and Trial will follow in stages, and we will post here as each is enabled.

Our API, dashboard and station.railway.com remain affected.

We will continue posting updates at least every 30 minutes, and sooner if we have more information. The next update will be at 20:30 UTC.

We have mitigated some issues impacting builds and are continuing to work on bringing builds back online.

We continue to expect builds for Enterprise workspaces to be available by 20:30 UTC. Pro, Hobby, then Free and Trial will follow in stages, and we will post here as each is enabled.

Our API, dashboard and station.railway.com remain affected.

We will continue posting updates at least every 30 minutes, and sooner if we have more information. The next update will be at 20:25 UTC

Earlier today an issue affecting multiple systems led us to pause builds across the platform. We are now working to bring builds back.

We expect builds for Enterprise workspaces to be available by 20:30 UTC. Pro, Hobby, then Free and Trial will follow in stages, and we will post here as each is enabled.

Our API, dashboard and station.railway.com remain affected.

We will continue posting updates at least every 30 minutes, and sooner if anything changes. The next update will be at 20:00 UTC.

Builds and deployments remain paused, and our API, dashboard and station.railway.com are still affected.

When we re-enable builds, we will do it in stages to keep the platform stable as capacity comes back: Enterprise workspaces first, followed by Pro, then Hobby, then Free and Trial. We will post here as each stage is enabled.

We will continue posting updates at least every 30 minutes, and sooner if anything changes. The next update will be at 19:45 UTC.

Work on the issues affecting our API, dashboard, and the build and deployment pipeline is ongoing. Builds and deployments remain paused, and station.railway.com is still unavailable. We do not have new information to share at this time.

We will continue posting updates at least every 30 minutes, and sooner if anything changes. The next update will be at 19:15 UTC.

Builds and deployments remain paused, and our API, dashboard and station.railway.com are still affected. We do not have new information to share at this time.

We will continue posting updates at least every 30 minutes, and sooner if anything changes. The next update will be at 18:45 UTC.

There is no change to report. Our API, dashboard, and the build and deployment pipeline remain affected, builds and deployments are still paused, and station.railway.com remains unavailable.

We will continue posting updates at least every 30 minutes, and sooner if anything changes. The next update will be at 18:15 UTC.

We are still working to resolve the issues affecting our API, dashboard, and the build and deployment pipeline. Builds and deployments remain paused, and our support site (station.railway.com) is unavailable.

We do not have further detail to share yet. We will post updates at least every 30 minutes, and sooner if we have more information. The next update will be at 17:45 UTC.

We are still working to resolve the issues affecting our API, dashboard, and the build and deployment pipeline. Builds and deployments remain paused, and our support site (station.railway.com) is also unavailable, so new support requests cannot be submitted there at this time.

There is no change since our last update. Builds remain paused and some API features are still unavailable. Our support platform is still down as well. We are continuing to work on a fix and will post updates here.

Builds remain paused. Our API is back up, but some features remain unavailable.

We are working on restoring access to our support platform and will continue providing updates here.

We have identified the issue and are working on a fix. While we do, the Railway dashboard, API and CLI are unavailable, and new builds remain paused in all regions. Our support site is also affected, so replies to support requests will be delayed.

We are seeing issues on Railways backend as well. We are still investigating this issue.

We are currently investigating this issue