Hosting / PaaS / Railway

Railway

SEV 2 · BLEEDING · 37h 17m

Since Jul 2026 · 28 incidents · status.railway.com · checked just now

CompareStatus page
GradeFLast 90 days
BPRODDSHIP
Happening now
Oct 21, 2026ongoingSEV 2 · SECURITY
Railway Platform OutageRailway builds and deployments were stuck, queued, or failing for days, and Hobby, Free and Trial builds stayed disabled while Pro and Enterprise recovered. A security incident invalidated API and project tokens, so users must create new ones. New signups were paused. The text does not say customer apps went down. The incident was still open at the last update.AI-graded · Builds +2
Why this grade
  1. RULES · SEV 1
    Sev 2 because Builds had a major outage, raised to Sev 1 for security
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE · SECURITY
    Builds and deployments were delayed or failing for days across tiers, Hobby and Free builds stayed disabled, and API tokens were invalidated after a security incident.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
55 updates
  1. 07:24 UTC · investigating
    We are currently investigating this issue
  2. 08:28 UTC · investigating
    We are seeing issues on Railways backend as well. We are still investigating this issue.
  3. 09:28 UTC · identified
    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.
  4. 11:33 UTC · identified
    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.
  5. 13:40 UTC · identified
    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.
  6. 16:29 UTC · identified
    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.
  7. 17:18 UTC · identified
    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.
  8. 17:45 UTC · identified
    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.
  9. 18:15 UTC · identified
    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.
  10. 18:45 UTC · identified
    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.
  11. 19:15 UTC · identified
    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.
  12. 19:30 UTC · identified
    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.
  13. 19:55 UTC · identified
    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
  14. 20:19 UTC · identified
    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.
  15. 20:30 UTC · identified
    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.
  16. 20:35 UTC · identified
    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.
  17. 21:01 UTC · identified
    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.
  18. 21:59 UTC · identified
    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.
  19. 22:10 UTC · identified
    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.
  20. 22:37 UTC · identified
    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.
  21. 22:45 UTC · identified
    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.
  22. 00:22 UTC · identified
    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.
  23. 01:22 UTC · identified
    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
  24. 02:19 UTC · identified
    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.
  25. 03:00 UTC · identified
    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.
  26. 03:32 UTC · identified
    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.
  27. 04:00 UTC · identified
    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.
  28. 04:17 UTC · identified
    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.
  29. 04:39 UTC · identified
    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.
  30. 04:52 UTC · identified
    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.
  31. 05:20 UTC · identified
    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.
  32. 06:01 UTC · identified
    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.
  33. 06:12 UTC · identified
    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.
  34. 06:29 UTC · identified
    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.
  35. 07:11 UTC · identified
    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.
  36. 08:01 UTC · identified
    Deployments are going live, but many are taking longer than usual to start and may stay queued for some time. To avoid adding to the wait, please do not trigger the same deployment more than once. We are working to bring deployment times back to normal. 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:45 UTC at the latest.
  37. 08:44 UTC · identified
    There is no change since our last update. Many deployments are still queued, and wait times may be longer than earlier. To avoid adding to the wait, please do not trigger the same deployment more than once. We are continuing to work on bringing deployment times back to normal. 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 09:30 UTC at the latest.
  38. 09:28 UTC · identified
    Some builds are failing more often than usual, and we are working to bring error rates back down. Many deployments are also still queued, and wait times remain longer than usual. To avoid adding to the wait, please do not trigger the same deployment more than once. 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 10:15 UTC at the latest.
  39. 10:15 UTC · identified
    There is no change since our last update. Some builds are still failing more often than usual, and many deployments remain queued with longer than usual wait times. We are continuing to work on both. 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 11:00 UTC at the latest.
  40. 11:01 UTC · identified
    The number of queued deployments has stopped growing, and queued deployments are now starting, though more slowly than usual. To avoid adding to the wait, please do not trigger the same deployment more than once. We are also continuing to work on build error rates. 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 11:45 UTC at the latest.
  41. 11:47 UTC · identified
    Deployment wait times are coming down as we work through the queue, though some deployments may still take longer than usual to start. 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 12:30 UTC at the latest.
  42. 12:30 UTC · identified
    Deployment wait times are improving significantly as we work through the queue, and most deployments are now starting much sooner. Some may still take longer than usual to start. We are continuing to work on bringing deployment times fully back to normal. 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 13:15 UTC at the latest.
  43. 13:16 UTC · identified
    We have almost worked through the queue of delayed deployments, and wait times are close to normal. A small number of deployments may still take longer than usual to start. 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 14:00 UTC at the latest.
  44. 13:53 UTC · identified
    We have worked through the queue of delayed deployments, and deployments for Pro and Enterprise workspaces are now starting at normal speed. No action is needed for deployments that were queued. We are continuing to work on enabling builds for Hobby, then Free and Trial, and will post here as each is enabled. We will provide another update by 14:45 UTC at the latest.
  45. 14:50 UTC · identified
    Deployments for Pro and Enterprise workspaces are running a little slower than usual, and some may take longer than expected to complete. We are working to bring them back to normal speed. We are continuing to work on enabling builds for Hobby, then Free and Trial, and will post here as each is enabled. We will provide another update by 15:30 UTC at the latest.
  46. 15:29 UTC · identified
    Deployments for Pro and Enterprise workspaces continue to run a little slower than usual, and some may take longer than expected to complete. We are working to bring them back to normal speed. We will post here when builds for Hobby, Free and Trial are re-enabled. We will provide another update by 16:15 UTC at the latest.
  47. 16:14 UTC · identified
    Deployments for Pro and Enterprise workspaces are now running at normal speed. We are working to get builds enabled for Hobby next, and will post here when they are enabled. We are aware that some builds are failing shortly after they start, and we are working on a fix. If your build fails this way, please retry it once. We will provide another update by 17:00 UTC at the latest.
  48. 17:00 UTC · identified
    The API is now fully restored, including features that were temporarily unavailable. API tokens and Project Tokens created before the security incident remain invalidated, so if you use the Public API or the cli with a token, please create a new token. Deployments for both Pro and Enterprise workspaces have been available since 06:30 UTC and continue to run at normal speed. The build failure errors we were seeing before should now be resolved. If your build does still fail shortly after start, please retry it once. We are working to enable builds for Hobby, then Free and Trial, later today. We will post here as each is enabled, and will update this page if that changes. Once this incident is resolved, we will publish a full incident report on our blog and link to it from this page. We will provide another update by 17:45 UTC at the latest.
  49. 17:43 UTC · identified
    There is no change since our last update. Builds and deployments for Pro and Enterprise workspaces continue to run at normal speed. If your build fails shortly after it starts, please retry it once. We are continuing to work on enabling builds for Hobby, which will be next, followed by Free and Trial. We will post here as each is enabled. We will provide another update by 18:30 UTC at the latest.
  50. 18:30 UTC · identified
    Builds and deployments for Pro and Enterprise workspaces are running normally, and there is no change to report since our last update. We are still working on enabling builds for Hobby, and will post here as soon as they are available. Free and Trial will follow after Hobby. If a build fails shortly after it starts, please retry it. We will provide another update by 19:15 UTC at the latest.
  51. 18:42 UTC · identified
    We are aware that some deployments in US West are failing, even after their build completes successfully. We are investigating and working on a fix. Deployments in other regions are not affected by this issue. We will provide another update by 19:15 UTC at the latest.
  52. 18:49 UTC · identified
    Deployments in US West are working normally again. If a deployment in US West failed after its build completed, please redeploy the service. Builds and deployments for Pro and Enterprise workspaces continue to run normally, and we are still working on enabling builds for Hobby. We will post here as soon as they are available. We will provide another update by 19:15 UTC at the latest.
  53. 19:06 UTC · identified
    We have temporarily paused new signups so we can focus on making sure everything is working well for existing customers. We will re-enable signups once that is done, and will post here when they are available again. Builds and deployments for Pro and Enterprise workspaces continue to run normally. We are still working on enabling builds for Hobby, followed by Free and Trial, and will post here as each is enabled. We will provide another update by 19:45 UTC at the latest.
  54. 19:42 UTC · identified
    There is no change since our last update. New signups remain temporarily paused while we focus on existing customers. Builds and deployments for Pro and Enterprise workspaces are running normally, and enabling builds for Hobby remains our current focus. Free and Trial will follow after Hobby. We will provide another update by 20:30 UTC at the latest.
  55. 20:29 UTC · identified
    Builds and deployments for Pro and Enterprise workspaces continue to run normally, and there is no other change since our last update. We are still working on enabling builds for Hobby, with Free and Trial to follow, and will post here as each is enabled. New signups remain temporarily paused. We will provide another update by 21:15 UTC at the latest.
Source
6 components affected5 major outage · 1 partial outageRailway 2 · EU West (Amsterdam, Netherlands) 1 · Southeast Asia (Singapore) 1 · +2 more
All 6
  • Buildsmajor outage
  • Support & Community — station.railway.commajor outage
  • Buildsmajor outage
  • Buildsmajor outage
  • Buildsmajor outage
  • API — backboard.railway.compartial outage

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade F
IncidentsEverything posted on the status page except scheduled maintenance.
280 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
49m
LongestLongest single incident, start to resolved.
37h 17m
Since lastTime since the last counted incident was resolved.
ongoing

By area

BProduction
5INCIDENTS
11h 07mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 1y
SEV 2Oct 3, 2026 · 7h 50mServices and databases unavailable for some users in US West
SEV 2Aug 10, 2026 · 2h 08mConnectivity issues in US West
SEV 2Aug 29, 2026 · 40mStorage and networking issues affecting some services in US West
Most hit
Compute (US West)2
Networking — Public (US West)2
Storage (US West)1
Networking — Public (US East)1
Worse. 5 in the last 6 months, 0 in the 6 before.
DShipping
23INCIDENTS
3d 0hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 1y
SEV 2Oct 20, 2026 · 3h 53mNew builds are temporarily paused
SEV 3 · SECURITYOct 21, 2026 · ongoingRailway Platform Outage
SEV 3Aug 17, 2026 · 7h 30mGitHub is experiencing elevated error rates
Most hit
Deployments (US West)9
Deployments (EU West)9
Deployments (US East)8
Deployments (Southeast Asia)8
Worse. 23 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production web app, per month512 MB app on all month, 1M requests, 100 GB out, commercial use, one seat. Cheapest plan that runs it.
Hobby4 of 8 cheaper · Heroku: cheaper, better grade
~$12/mo
Hobby plan (includes $5 of usage)$5
512 MB RAM all month at $10/GB$5
0.1 vCPU average at $20/vCPU$2
100 GB egress at $0.05/GB$5
Included usage credit−$5

Railway bills actual CPU use; this assumes the app averages 10% of one vCPU. docs.railway.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 28 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down7
Sev 3 · Can't shipCan't deploy, build or manage it13
Sev 4 · PapercutDocs, status page, slow dashboard8
1 security incident

When it breaks

Start times, last 12 months, UTC.

What breaks

Deployments (US West)9 incidents
Deployments (EU West)9 incidents
Deployments (US East)8 incidents
Deployments (Southeast Asia)8 incidents
Builds (US West)6 incidents
Builds (EU West)6 incidents

Communication

Updates eachStatus page updates per incident, on average.
5.4Last 12 months
Update gapMedian time between status page updates during an incident.
28mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 7Sev 1–2

Incident history

Show all 28
Oct 21, 2026ongoingSEV 2 · SECURITY
Railway Platform OutageRailway builds and deployments were stuck, queued, or failing for days, and Hobby, Free and Trial builds stayed disabled while Pro and Enterprise recovered. A security incident invalidated API and project tokens, so users must create new ones. New signups were paused. The text does not say customer apps went down. The incident was still open at the last update.AI-graded · Builds +2
Why this grade
  1. RULES · SEV 1
    Sev 2 because Builds had a major outage, raised to Sev 1 for security
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE · SECURITY
    Builds and deployments were delayed or failing for days across tiers, Hobby and Free builds stayed disabled, and API tokens were invalidated after a security incident.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
55 updates
  1. 07:24 UTC · investigating
    We are currently investigating this issue
  2. 08:28 UTC · investigating
    We are seeing issues on Railways backend as well. We are still investigating this issue.
  3. 09:28 UTC · identified
    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.
  4. 11:33 UTC · identified
    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.
  5. 13:40 UTC · identified
    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.
  6. 16:29 UTC · identified
    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.
  7. 17:18 UTC · identified
    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.
  8. 17:45 UTC · identified
    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.
  9. 18:15 UTC · identified
    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.
  10. 18:45 UTC · identified
    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.
  11. 19:15 UTC · identified
    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.
  12. 19:30 UTC · identified
    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.
  13. 19:55 UTC · identified
    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
  14. 20:19 UTC · identified
    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.
  15. 20:30 UTC · identified
    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.
  16. 20:35 UTC · identified
    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.
  17. 21:01 UTC · identified
    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.
  18. 21:59 UTC · identified
    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.
  19. 22:10 UTC · identified
    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.
  20. 22:37 UTC · identified
    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.
  21. 22:45 UTC · identified
    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.
  22. 00:22 UTC · identified
    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.
  23. 01:22 UTC · identified
    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
  24. 02:19 UTC · identified
    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.
  25. 03:00 UTC · identified
    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.
  26. 03:32 UTC · identified
    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.
  27. 04:00 UTC · identified
    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.
  28. 04:17 UTC · identified
    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.
  29. 04:39 UTC · identified
    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.
  30. 04:52 UTC · identified
    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.
  31. 05:20 UTC · identified
    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.
  32. 06:01 UTC · identified
    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.
  33. 06:12 UTC · identified
    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.
  34. 06:29 UTC · identified
    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.
  35. 07:11 UTC · identified
    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.
  36. 08:01 UTC · identified
    Deployments are going live, but many are taking longer than usual to start and may stay queued for some time. To avoid adding to the wait, please do not trigger the same deployment more than once. We are working to bring deployment times back to normal. 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:45 UTC at the latest.
  37. 08:44 UTC · identified
    There is no change since our last update. Many deployments are still queued, and wait times may be longer than earlier. To avoid adding to the wait, please do not trigger the same deployment more than once. We are continuing to work on bringing deployment times back to normal. 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 09:30 UTC at the latest.
  38. 09:28 UTC · identified
    Some builds are failing more often than usual, and we are working to bring error rates back down. Many deployments are also still queued, and wait times remain longer than usual. To avoid adding to the wait, please do not trigger the same deployment more than once. 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 10:15 UTC at the latest.
  39. 10:15 UTC · identified
    There is no change since our last update. Some builds are still failing more often than usual, and many deployments remain queued with longer than usual wait times. We are continuing to work on both. 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 11:00 UTC at the latest.
  40. 11:01 UTC · identified
    The number of queued deployments has stopped growing, and queued deployments are now starting, though more slowly than usual. To avoid adding to the wait, please do not trigger the same deployment more than once. We are also continuing to work on build error rates. 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 11:45 UTC at the latest.
  41. 11:47 UTC · identified
    Deployment wait times are coming down as we work through the queue, though some deployments may still take longer than usual to start. 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 12:30 UTC at the latest.
  42. 12:30 UTC · identified
    Deployment wait times are improving significantly as we work through the queue, and most deployments are now starting much sooner. Some may still take longer than usual to start. We are continuing to work on bringing deployment times fully back to normal. 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 13:15 UTC at the latest.
  43. 13:16 UTC · identified
    We have almost worked through the queue of delayed deployments, and wait times are close to normal. A small number of deployments may still take longer than usual to start. 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 14:00 UTC at the latest.
  44. 13:53 UTC · identified
    We have worked through the queue of delayed deployments, and deployments for Pro and Enterprise workspaces are now starting at normal speed. No action is needed for deployments that were queued. We are continuing to work on enabling builds for Hobby, then Free and Trial, and will post here as each is enabled. We will provide another update by 14:45 UTC at the latest.
  45. 14:50 UTC · identified
    Deployments for Pro and Enterprise workspaces are running a little slower than usual, and some may take longer than expected to complete. We are working to bring them back to normal speed. We are continuing to work on enabling builds for Hobby, then Free and Trial, and will post here as each is enabled. We will provide another update by 15:30 UTC at the latest.
  46. 15:29 UTC · identified
    Deployments for Pro and Enterprise workspaces continue to run a little slower than usual, and some may take longer than expected to complete. We are working to bring them back to normal speed. We will post here when builds for Hobby, Free and Trial are re-enabled. We will provide another update by 16:15 UTC at the latest.
  47. 16:14 UTC · identified
    Deployments for Pro and Enterprise workspaces are now running at normal speed. We are working to get builds enabled for Hobby next, and will post here when they are enabled. We are aware that some builds are failing shortly after they start, and we are working on a fix. If your build fails this way, please retry it once. We will provide another update by 17:00 UTC at the latest.
  48. 17:00 UTC · identified
    The API is now fully restored, including features that were temporarily unavailable. API tokens and Project Tokens created before the security incident remain invalidated, so if you use the Public API or the cli with a token, please create a new token. Deployments for both Pro and Enterprise workspaces have been available since 06:30 UTC and continue to run at normal speed. The build failure errors we were seeing before should now be resolved. If your build does still fail shortly after start, please retry it once. We are working to enable builds for Hobby, then Free and Trial, later today. We will post here as each is enabled, and will update this page if that changes. Once this incident is resolved, we will publish a full incident report on our blog and link to it from this page. We will provide another update by 17:45 UTC at the latest.
  49. 17:43 UTC · identified
    There is no change since our last update. Builds and deployments for Pro and Enterprise workspaces continue to run at normal speed. If your build fails shortly after it starts, please retry it once. We are continuing to work on enabling builds for Hobby, which will be next, followed by Free and Trial. We will post here as each is enabled. We will provide another update by 18:30 UTC at the latest.
  50. 18:30 UTC · identified
    Builds and deployments for Pro and Enterprise workspaces are running normally, and there is no change to report since our last update. We are still working on enabling builds for Hobby, and will post here as soon as they are available. Free and Trial will follow after Hobby. If a build fails shortly after it starts, please retry it. We will provide another update by 19:15 UTC at the latest.
  51. 18:42 UTC · identified
    We are aware that some deployments in US West are failing, even after their build completes successfully. We are investigating and working on a fix. Deployments in other regions are not affected by this issue. We will provide another update by 19:15 UTC at the latest.
  52. 18:49 UTC · identified
    Deployments in US West are working normally again. If a deployment in US West failed after its build completed, please redeploy the service. Builds and deployments for Pro and Enterprise workspaces continue to run normally, and we are still working on enabling builds for Hobby. We will post here as soon as they are available. We will provide another update by 19:15 UTC at the latest.
  53. 19:06 UTC · identified
    We have temporarily paused new signups so we can focus on making sure everything is working well for existing customers. We will re-enable signups once that is done, and will post here when they are available again. Builds and deployments for Pro and Enterprise workspaces continue to run normally. We are still working on enabling builds for Hobby, followed by Free and Trial, and will post here as each is enabled. We will provide another update by 19:45 UTC at the latest.
  54. 19:42 UTC · identified
    There is no change since our last update. New signups remain temporarily paused while we focus on existing customers. Builds and deployments for Pro and Enterprise workspaces are running normally, and enabling builds for Hobby remains our current focus. Free and Trial will follow after Hobby. We will provide another update by 20:30 UTC at the latest.
  55. 20:29 UTC · identified
    Builds and deployments for Pro and Enterprise workspaces continue to run normally, and there is no other change since our last update. We are still working on enabling builds for Hobby, with Free and Trial to follow, and will post here as each is enabled. New signups remain temporarily paused. We will provide another update by 21:15 UTC at the latest.
Source
Oct 20, 20263h 53mSEV 2
New builds are temporarily pausedNew builds were paused for all Railway workspaces in all four build regions from about 17:03 to 20:56 UTC on October 20. Running services were unaffected. Builds returned in stages, starting with Enterprise. Deploys made during the pause must be triggered again.AI-graded · Builds (US West) +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Builds (US West) had a major outage
  2. CLAUDE · SEV 2 · GLOBAL · HIGH CONFIDENCE
    New builds were paused for all workspaces across four regions for about four hours; running services were not affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
7 updates
  1. 17:03 UTC · investigating
    An issue affecting builds was reported; new builds paused for most workspaces. Running services not affected.
  2. 17:18 UTC · identified
    Build issue identified, fix in progress. New builds paused for all workspaces.
  3. 19:10 UTC · identified
    Builds still paused for all workspaces; to return in stages.
  4. 19:59 UTC · identified
    Fix applied; builds resuming, starting with Enterprise workspaces.
  5. 20:20 UTC · monitoring
    Builds enabled for Pro workspaces.
  6. 20:43 UTC · monitoring
    Builds enabled for Hobby workspaces.
  7. 20:56 UTC · resolved
    Builds resumed for all workspaces. Deploys made during the pause must be triggered again.
Source
Oct 13, 202648mSEV 4
Builds are taking longer than usualRailway builds in the US West region ran slower than usual from 16:12 to 17:00 UTC. The cause was an issue in the regional build infrastructure, which was fixed and the queue cleared. Builds were slower but not reported as failing.AI-graded · regional · Builds (US West)
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds (US West) had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · HIGH CONFIDENCE
    Builds in US West ran longer than usual for about 48 minutes; deploys still completed, just slower.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 16:12 UTC · investigating
    Builds running longer than usual.
  2. 16:35 UTC · identified
    Issue in US West build infrastructure identified.
  3. 16:39 UTC · identified
    Root cause found; fix rolling out.
  4. 16:45 UTC · monitoring
    US West build times recovering.
  5. 17:00 UTC · resolved
    Build times back to normal; queue cleared.
Source
Oct 10, 20265mSEV 4
Central Station not loading for some usersRailway's community forum site station.railway.com was unavailable for some users for about five minutes; the product was not described as affected.AI-graded · Support & Community — station.railway.com
Why this grade
  1. RULES · SEV 4
    Sev 4 because Support & Community — station.railway.com had degraded performance
  2. CLAUDE · SEV 4 · UNCLEAR · HIGH CONFIDENCE
    Railway's community forum site station.railway.com was unavailable for some users for about five minutes; the product was not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 01:34 UTC · investigating
    station.railway.com reported unavailable.
  2. 01:39 UTC · resolved
    Resolved.
Source
Oct 9, 202638mSEV 3
Builds and deployments failing to pull images from Docker HubBuilds and deploys that pull images from Docker Hub failed with 429 rate-limit errors from 21:29 to 22:07 UTC. Railway traced it to an ongoing Docker Hub incident. Pulls recovered by 22:03 and the incident was resolved at 22:07; affected deploys needed a redeploy.AI-graded · some customers · Image Registry — Dockerhub
Why this grade
  1. RULES · SEV 3
    Sev 3 because Image Registry — Dockerhub had a partial outage
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Builds and deploys using Docker Hub images failed with 429 errors for about 38 minutes; other image sources were not mentioned.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 21:29 UTC · investigating
    Builds and deploys using Docker Hub images hitting 429 errors.
  2. 21:49 UTC · identified
    Traced to an ongoing Docker Hub incident.
  3. 22:03 UTC · monitoring
    Docker Hub pulls succeeding again.
  4. 22:07 UTC · resolved
    Resolved. Redeploy anything that failed.
Source
Oct 5, 202635mSEV 4
Dashboard loading issuesRailway dashboard loaded slowly or not at all for some users for about 35 minutes; deployed apps were not described as affected.AI-graded · some customers · Dashboard — railway.com
Why this grade
  1. RULES · SEV 4
    Sev 4 because Dashboard — railway.com had degraded performance
  2. CLAUDE · SEV 4 · SUBSET · HIGH CONFIDENCE
    Railway dashboard loaded slowly or not at all for some users for about 35 minutes; deployed apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 15:37 UTC · investigating
    Dashboard loading slowly or not at all for some users.
  2. 15:57 UTC · monitoring
    Dashboard response times recovering.
  3. 16:12 UTC · resolved
    API pods had event loop delays; capacity scaled up.
Source
Oct 5, 20261h 18mSEV 3
GitHub-triggered builds are delayedGitHub-triggered builds queued or started slowly from 14:55 to 16:13 UTC on October 5 across US West, US East, EU West and Southeast Asia. The cause was identified and fixed, and the build queue drained by resolution. Running apps were not reported as affected.AI-graded · Builds (US West) +4
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds (US West) had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    GitHub-triggered builds queued or started slowly across all regions for about 78 minutes; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 14:55 UTC · investigating
    GitHub-triggered builds queuing or starting slowly.
  2. 15:40 UTC · identified
    Issue identified; fix in progress.
  3. 15:52 UTC · monitoring
    Recovery underway; queue draining.
  4. 16:13 UTC · resolved
    Build queue drained in all regions.
Source
Oct 4, 20260mSEV 2
Slow attached storage for some users in US WestAttached storage in US West was slow for some users, slowing services, databases and deploys, with some crash loops.AI-graded · regional · Storage (US West)
Why this grade
  1. RULES · SEV 1
    Sev 1 because Storage (US West) had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Attached storage in US West was slow for some users, slowing services, databases and deploys, with some crash loops.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 02:47 UTC · identified
    Cause of slow attached storage found; slow services, databases and deploys, some crash loops.
Source
Oct 3, 20267h 50mSEV 2
Services and databases unavailable for some users in US WestServices and databases were unreachable on some US West hosts for about eight hours; other regions were not listed as affected.AI-graded · regional · Compute (US West)
Why this grade
  1. RULES · SEV 1
    Sev 1 because Compute (US West) had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Services and databases were unreachable on some US West hosts for about eight hours; other regions were not listed as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 11:43 UTC · identified
    Some US West hosts unresponsive; services and databases unreachable. Hosts being restarted.
  2. 17:21 UTC · monitoring
    Affected hosts restarted; services recovering.
  3. 19:33 UTC · resolved
    US West outage affecting services and databases fixed.
Source
Sep 30, 202629mSEV 2
Domain routing disruptionDomains on Railway returned 404s across four public networking regions for about 5 minutes after a config rollout.AI-graded · Networking — Public (US West) +3
Why this grade
  1. RULES · SEV 1
    Sev 1 because Networking — Public (US West) had a partial outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Domains on Railway returned 404s across four public networking regions for about 5 minutes after a config rollout.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 07:48 UTC · monitoring
    Domains on Railway returned 404s for about 5 minutes; mitigated.
  2. 08:17 UTC · resolved
    A config rollout caused routing errors for about 5 minutes.
Source
Sep 29, 20263h 46mSEV 3
API degradation causing slow or stuck deploymentsDeployments were slow or stuck across all four regions for about 3h45m; the text does not say running apps were affected.AI-graded · Deployments (US West) +4
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Deployments were slow or stuck across all four regions for about 3h45m; the text does not say running apps were affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 15:29 UTC · investigating
    API issue causing slow or stuck deployments.
  2. 18:37 UTC · monitoring
    Recovering; Hobby deployments re-enabled.
  3. 19:15 UTC · resolved
    Deployment backlog cleared.
Source
Sep 23, 202649mSEV 4
Builds are slow in EU WestBuilds in the EU West region were slow and queued for about 50 minutes; running apps were not described as affected.AI-graded · regional · Builds (EU West)
Why this grade
  1. RULES · SEV 3
    Sev 3 because Builds (EU West) had degraded performance
  2. CLAUDE · SEV 4 · REGIONAL · MEDIUM CONFIDENCE
    Builds in the EU West region were slow and queued for about 50 minutes; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 13:24 UTC · investigating
    Builds in EU West taking longer than expected.
  2. 13:53 UTC · investigating
    Possible deployment system issue queuing EU West builds.
  3. 14:13 UTC · identified
    Root cause found; fix in progress.
Source
Aug 31, 20260mSEV 3
Storage bucket creation is degradedCreating storage buckets and access keys may fail across four regions; existing buckets are not described as affected.AI-graded · Storage Buckets (US West) +3
Why this grade
  1. RULES · SEV 1
    Sev 1 because Storage Buckets (US West) had a partial outage
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Creating storage buckets and access keys may fail across four regions; existing buckets are not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
1 update
  1. 15:31 UTC · investigating
    Creating storage buckets and access keys may fail.
Source
Aug 29, 202640mSEV 2
Storage and networking issues affecting some services in US WestA hardware fault in US West storage left some services unavailable, stuck restarting, or slow, and degraded private networking for about 40 minutes. The faulty hardware was removed and services recovered. No data loss was reported.AI-graded · regional · Compute (US West) +2
Why this grade
  1. RULES · SEV 1
    Sev 1 because Compute (US West) had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some US West services were unavailable, stuck restarting, or slow for about 40 minutes due to a storage hardware fault; other regions were unaffected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 01:38 UTC · investigating
    Some US West services unavailable, stuck restarting, or slow.
  2. 01:45 UTC · investigating
    Traced to US West storage; private networking degraded.
  3. 02:08 UTC · monitoring
    Hardware fault isolated; recovery underway.
  4. 02:18 UTC · resolved
    Faulty hardware removed; services recovered.
Source
Aug 28, 20263h 39mSEV 3
Deployments slow to startDeployments in US West, US East, EU West and Southeast Asia started slowly for about four hours. A networking fault on one host queued deployments; the host was removed, workers were unstable while the queue drained, and the backlog was cleared before throughput returned to normal.AI-graded · Deployments (US West) +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Deployments started slowly in four regions for about four hours after a networking fault on one host; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 23:59 UTC · investigating
    Deployments starting slowly.
  2. 00:20 UTC · monitoring
    Networking fault on one host queued deployments; host removed.
  3. 00:37 UTC · investigating
    Some workers unstable while the queue drains.
  4. 03:05 UTC · investigating
    Working through the deployment backlog.
  5. 03:33 UTC · monitoring
    Most of the backlog cleared.
  6. 03:38 UTC · resolved
    Deployment delays fixed; throughput normal.
Source
Aug 20, 20261mSEV 4
Delayed deploys in AMSDeploys in the AMS region were briefly delayed for about a minute, then returned to normal.AI-graded · one location · Deployments (EU West)
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (EU West) had degraded performance
  2. CLAUDE · SEV 4 · LOCAL · MEDIUM CONFIDENCE
    Deploys in the AMS region were briefly delayed for about a minute, then returned to normal.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 18:43 UTC · monitoring
    Deploys in AMS briefly delayed; back to normal.
  2. 18:44 UTC · resolved
    Resolved.
Source
Aug 20, 20262h 53mSEV 3
Deployments are slowDeployments queued and were slow to start or finish in US West, US East, EU West and Southeast Asia from 15:27 to 18:20 UTC on August 20. A Google Cloud infrastructure issue caused pipeline congestion. Deployments were briefly paused, the pause was lifted at 17:31, and the queue cleared by resolution.AI-graded · regional · Deployments (US West) +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had a partial outage
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Deployments queued and stalled across four regions for about three hours; running apps were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 15:27 UTC · investigating
    Deployments queuing and slow to start or finish.
  2. 15:56 UTC · identified
    Google Cloud infrastructure issue causing pipeline congestion.
  3. 16:15 UTC · identified
    Mitigation underway; deployments may be paused.
  4. 17:29 UTC · identified
    Throughput improving; still slow.
  5. 17:31 UTC · monitoring
    Deployment pause lifted; queue draining.
  6. 18:20 UTC · resolved
    Deployments normal; queue cleared.
Source
Aug 18, 20262h 58mSEV 3
Deployments are slow to progress and are prone to timeout failureRailway deployments in four regions were stuck initializing and some builds timed out or failed from about 23:19 to 02:17 UTC. An infrastructure load issue was identified, Pro builds were restored first, and builds and the API returned to normal after the queue recovered.AI-graded · regional · Deployments (US West) +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had degraded performance
  2. CLAUDE · SEV 3 · REGIONAL · MEDIUM CONFIDENCE
    Deployments stalled and timed out across four regions for about three hours; builds were slow and some failed.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 23:19 UTC · investigating
    Deployments stuck initializing longer than expected.
  2. 00:40 UTC · investigating
    Narrowing down the cause of delayed builds.
  3. 01:01 UTC · investigating
    Narrowing down the cause of delayed and failing builds.
  4. 01:16 UTC · identified
    Infrastructure load issue identified; Pro builds restored.
  5. 01:47 UTC · monitoring
    Build queues recovering; API slower meanwhile.
  6. 02:17 UTC · resolved
    Builds and API back to normal.
Source
Aug 18, 202655mSEV 3
Deployments are slow to progressDeployments stuck initializing longer than usual across four regions for about 55 minutes; no outage reported.AI-graded · Deployments (US West) +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had degraded performance
  2. CLAUDE · SEV 3 · GLOBAL · MEDIUM CONFIDENCE
    Deployments stuck initializing longer than usual across four regions for about 55 minutes; no outage reported.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 21:45 UTC · investigating
    Deployments stuck initializing longer than usual.
  2. 22:17 UTC · monitoring
    Traced to task queue processing; revert underway.
  3. 22:40 UTC · resolved
    Deployments back to normal speed.
Source
Aug 17, 20262h 02mSEV 4
Deployments queued longer than usualDeployments queued longer than normal in all four regions for about two hours; no outage reported.AI-graded · Deployments (US West) +3
Why this grade
  1. RULES · SEV 3
    Sev 3 because Deployments (US West) had degraded performance
  2. CLAUDE · SEV 4 · GLOBAL · HIGH CONFIDENCE
    Deployments queued longer than normal in all four regions for about two hours; no outage reported.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
3 updates
  1. 19:50 UTC · investigating
    Deployments queued longer than normal.
  2. 21:25 UTC · monitoring
    Fix live; deployment times improving.
  3. 21:52 UTC · resolved
    Deployment times normal in all regions.
Source

Peers, 90 days

Compare
HerokuGrade A+100.00% up0 incidentsMTTR –$7/moNetlifyGrade B100.00% up17 incidentsMTTR 34m~$20/moRenderGrade C100.00% up13 incidentsMTTR 1h 35m$21.25/moVercelGrade C100.00% up23 incidentsMTTR 47m~$20/moDigitalOceanGrade F100.00% up18 incidentsMTTR 4h 02m$6/moFly.ioGrade F99.38% up26 incidentsMTTR 44m$5.69/moRailwayGrade F100.00% up27 incidentsMTTR 55m~$12/moCloudflareGrade F100.00% up54 incidentsMTTR 1h 13m~$5/mo

README badge

Railway's live grade, for your README.

Railway grade badge
[![railway on downagain.dev](https://downagain.dev/badge/railway.svg)](https://downagain.dev/p/railway)