Railway Outage History

Started Oct 21, 2026, 07:24 AM UTC· resolved Oct 23, 2026, 10:06 PM UTC

1. investigating Oct 21, 2026, 07:24 AM UTC

   We are currently investigating this issue

2. investigating Oct 21, 2026, 08:28 AM UTC

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

3. identified Oct 21, 2026, 09:28 AM UTC

   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. identified Oct 21, 2026, 11:33 AM UTC

   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. identified Oct 21, 2026, 01:40 PM UTC

   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. identified Oct 21, 2026, 04:29 PM 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.

7. identified Oct 21, 2026, 05:18 PM 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.

8. identified Oct 21, 2026, 05:45 PM 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.

9. identified Oct 21, 2026, 06:15 PM 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.

10. identified Oct 21, 2026, 06:45 PM 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.

11. identified Oct 21, 2026, 07:15 PM 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.

12. identified Oct 21, 2026, 07:30 PM 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.

13. identified Oct 21, 2026, 07:55 PM 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

14. identified Oct 21, 2026, 08:19 PM UTC

    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. identified Oct 21, 2026, 08:30 PM 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.

16. identified Oct 21, 2026, 08:35 PM UTC

    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. identified Oct 21, 2026, 09:01 PM UTC

    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. identified Oct 21, 2026, 09:59 PM UTC

    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. identified Oct 21, 2026, 10:10 PM UTC

    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. identified Oct 21, 2026, 10:37 PM UTC

    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. identified Oct 21, 2026, 10:45 PM UTC

    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. identified Oct 22, 2026, 12:22 AM UTC

    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. identified Oct 22, 2026, 01:22 AM UTC

    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. identified Oct 22, 2026, 02:19 AM UTC

    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. identified Oct 22, 2026, 03:00 AM UTC

    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. identified Oct 22, 2026, 03:32 AM UTC

    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. identified Oct 22, 2026, 04:00 AM UTC

    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. identified Oct 22, 2026, 04:17 AM UTC

    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. identified Oct 22, 2026, 04:39 AM UTC

    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. identified Oct 22, 2026, 04:52 AM UTC

    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. identified Oct 22, 2026, 05:20 AM UTC

    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. identified Oct 22, 2026, 06:01 AM UTC

    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. identified Oct 22, 2026, 06:12 AM UTC

    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. identified Oct 22, 2026, 06:29 AM UTC

    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. identified Oct 22, 2026, 07:11 AM UTC

    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. identified Oct 22, 2026, 08:01 AM UTC

    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. identified Oct 22, 2026, 08:44 AM UTC

    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. identified Oct 22, 2026, 09:28 AM UTC

    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. identified Oct 22, 2026, 10:15 AM UTC

    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. identified Oct 22, 2026, 11:01 AM UTC

    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. identified Oct 22, 2026, 11:47 AM UTC

    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. identified Oct 22, 2026, 12:30 PM UTC

    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. identified Oct 22, 2026, 01:16 PM UTC

    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. identified Oct 22, 2026, 01:53 PM UTC

    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. identified Oct 22, 2026, 02:50 PM UTC

    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. identified Oct 22, 2026, 03:29 PM UTC

    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. identified Oct 22, 2026, 04:14 PM UTC

    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. identified Oct 22, 2026, 05:00 PM UTC

    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. identified Oct 22, 2026, 05:43 PM UTC

    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. identified Oct 22, 2026, 06:30 PM UTC

    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. identified Oct 22, 2026, 06:42 PM UTC

    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. identified Oct 22, 2026, 06:49 PM UTC

    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. identified Oct 22, 2026, 07:06 PM UTC

    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. identified Oct 22, 2026, 07:42 PM UTC

    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. identified Oct 22, 2026, 08:29 PM UTC

    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.

56. identified Oct 22, 2026, 09:08 PM UTC

    Builds are now available for Hobby workspaces. We’ve published Security Guides to help you take the next steps relevant to your setup. You can find them on our engineering blog: https://blog.railway.com/engineering Deployments are likely to take longer than usual for Hobby users while we work through demand. Once Hobby users are stable, we will work to enable builds for Free and Trial workspaces. New signups remain temporarily paused while we focus on existing customers. Builds and deployments for Pro and Enterprise workspaces continue to start normally but may take longer to complete. We will provide another update by 22:00 UTC at the latest.

57. identified Oct 22, 2026, 09:59 PM UTC

    Builds are enabled for Hobby, Pro and Enterprise workspaces. Builds and deployments are generally completing successfully but may still take longer than usual to complete. We will provide an update when we enable builds for Free and Trial workspaces. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 22:45 UTC at the latest.

58. identified Oct 22, 2026, 10:41 PM UTC

    Builds and deployments for Hobby, Pro and Enterprise workspaces are running at approximately normal speed. We are continuing to work on enabling builds for Free and Trial workspaces and will post here when they become available. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 23:30 UTC at the latest.

59. identified Oct 22, 2026, 10:49 PM UTC

    Builds are now available for Free and Trial workspaces, alongside Hobby, Pro and Enterprise. Builds and deployments across all five plans are running at approximately normal speed. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 23:30 UTC at the latest.

60. identified Oct 22, 2026, 11:22 PM UTC

    Builds and deployments for Enterprise, Pro, Hobby, Trial and Free workspaces continue to run at approximately normal speed. We are working to publish our Preliminary Incident Report soon. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 00:15 UTC on October 23 at the latest.

61. identified Oct 23, 2026, 12:11 AM UTC

    Builds and deployments across Enterprise, Pro, Hobby, Trial and Free workspaces continue to run at approximately normal speed. We remain on track to publish our Preliminary Incident Report soon and will share it here when it is available. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 01:00 UTC on October 23 at the latest.

62. identified Oct 23, 2026, 12:51 AM UTC

    There are no meaningful changes since our last update. Builds and deployments for Enterprise, Pro, Hobby, Trial and Free workspaces are proceeding normally. We are continuing to work on completing our Preliminary Incident Report and will share it here when it is published. New signups remain temporarily paused while we focus on existing customers. We will provide another update by 02:00 UTC on October 23 at the latest.

63. identified Oct 23, 2026, 02:00 AM UTC

    We had been targeting publication of our Preliminary Incident Report tonight, but we need more time before it is ready to publish. We are notifying impacted customers by email now. Builds and deployments for Enterprise, Pro, Hobby, Trial and Free workspaces remain available and are proceeding normally. New signups remain temporarily paused while we focus on existing customers. We will share further updates as new information becomes available and link to the report here when it is published.

64. identified Oct 23, 2026, 02:19 AM UTC

    We are continuing to notify impacted customers by email. We will update this status page as soon as all notification emails have been sent. We will post an update not later than 03:00 UTC on October 23.

65. identified Oct 23, 2026, 03:00 AM UTC

    We are continuing to send notification emails to impacted customers. At the current pace, we expect this to take at least several more hours, but we cannot give a reliable estimate for when all emails will be sent. We will post an update once sending is complete, or sooner if there are any material changes. We apologize that we cannot provide a more definite timeline. We still plan to publish our Preliminary Incident Report around midday Eastern Time on October 23.

66. identified Oct 23, 2026, 07:37 AM UTC

    Builds may stay in a queued state while the Railway team deploys an upgrade to the build system. This update is not related to the security disclosure. New signups remain temporarily paused while we focus on existing customers.

67. identified Oct 23, 2026, 08:09 AM UTC

    Builds and deployments for Enterprise, Pro, Hobby, Trial and Free workspaces are proceeding normally. New signups remain temporarily paused while we focus on existing customers. We have notified customers with a very high likelihood of impact by email. We are still conducting forensic analysis to find more cohorts of likelihood of impact. The team still expects the preliminary report by noon EST.

68. identified Oct 23, 2026, 09:34 AM UTC

    Reminder: if you are facing issues with deployments, you may need to disconnect and reconnect your GitHub integration. Redeploying code from before the incident would not work and result in an error. Builds and deployments for workspaces continue to run normally, and there is no other change since our last update.

69. identified Oct 23, 2026, 04:15 PM UTC

    We are in the process of publishing the preliminary report. A clarifying addendum on outreach emails, the Railway engineering team has performed preliminary forensics on the intent of the attacker, as such, we have bucketed customers based on risk of exposure based on logs and data we have collected over the last 48 hours. We have already sent the emails to highest risk targeted workspaces. We are now actively sending emails to the remaining buckets of users where they are considered at risk. If you have known compromised use of a token, please reach out to [email protected] which will help us with our investigation.

70. identified Oct 23, 2026, 04:38 PM UTC

    The preliminary report is now available: https://blog.railway.com/p/preliminary-report-october-security-incident Our investigation is still ongoing and we are still reaching out to customers we believe are at risk. Our team will remain engaged on the matter until we have notified everyone we believe is at risk.

71. monitoring Oct 23, 2026, 07:18 PM UTC

    We’ve published our preliminary report on the October 21 security incident. This is an update on the existing incident, not a new incident. As of October 23 at 18:57:54 UTC, we have completed notifications to users whose workspaces met our criteria for increased risk. No further higher-risk notifications are pending based on our findings as of that time. If new findings change our assessment of your workspace, we will contact you directly. Workspaces outside those higher-risk groups are not confirmed safe from compromise. If you have not already done so, please rotate sensitive credentials stored in Railway environment variables during the incident, revoke the old credentials, update your variables, and redeploy dependent services. Continue reviewing provider activity for suspicious usage. If you have already completed these rotations since the incident was contained, this update alone does not require you to repeat them. For help, contact [email protected].

72. monitoring Oct 23, 2026, 08:43 PM UTC

    Builds are operational, but they may take longer than usual to start or finish while we work through redeploys across the platform. The Railway API and dashboard are fully functional. Our support and community site, station.railway.com, remains unavailable while we work on restoring our remaining non-critical services. For help in the meantime, contact [email protected]. New signups remain temporarily paused while we focus on existing customers. We will continue to monitor and post another update once build times are back to normal.

73. resolved Oct 23, 2026, 10:06 PM UTC

    This incident has been resolved. Builds, deployments, the Railway API, and the dashboard are operating normally. New signups remain temporarily paused while we focus on existing customers. station.railway.com remains unavailable, and we are tracking it in a separate notice here https://status.railway.com/incident/ZEO9X68O Our preliminary report on the October 21 security incident is available at https://blog.railway.com/p/preliminary-report-october-security-incident. If you have not already done so, please rotate sensitive credentials stored in Railway environment variables, revoke the old credentials, and redeploy dependent services. We apologize for the disruption. For help, contact [email protected].

Read the full incident report →

Started Oct 21, 2026, 02:49 AM UTC· resolved Oct 21, 2026, 02:51 AM UTC

1. investigating Oct 21, 2026, 02:49 AM UTC

   We have temporarily paused builds for workspaces for Free, Trial and Hobby plans. New deployments for these workspaces will stay queued until builds resume. Services that are already running are not affected. Builds for Pro and Enterprise workspaces are processing normally.

2. resolved Oct 21, 2026, 02:51 AM UTC

   Dismissed as a notice. No impact.

Read the full incident report →

Started Oct 20, 2026, 05:03 PM UTC· resolved Oct 20, 2026, 08:56 PM UTC

1. investigating Oct 20, 2026, 05:03 PM UTC

   We are aware of an issue affecting builds and have temporarily paused new builds for most workspaces while we investigate. Deploys triggered during this period will need to be triggered again once we resume builds. Services that are already deployed and running are not affected. We are actively investigating and will provide updates as we learn more.

2. identified Oct 20, 2026, 05:18 PM UTC

   We have identified the issue affecting builds and are working on a fix. While we do, new builds are now paused for all workspaces. Deploys triggered during this period will need to be triggered again once we resume builds. Services that are already deployed and running are not affected. We will provide further updates as we make progress.

3. identified Oct 20, 2026, 07:10 PM UTC

   We are continuing to work on the issue affecting builds. Builds remain paused for all workspaces while we do, and we will bring them back in stages once we're confident everything is working as expected. Deploys triggered during this period will need to be triggered again once builds resume. Services that are already deployed and running are not affected. We'll share another update as soon as builds begin to resume.

4. identified Oct 20, 2026, 07:59 PM UTC

   We have applied a fix and are gradually resuming builds. Builds are now enabled for Enterprise workspaces, and we are working to resume builds for all other workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for more workspaces.

5. monitoring Oct 20, 2026, 08:20 PM UTC

   Builds are now enabled for Pro workspaces, in addition to Enterprise. We are working to resume builds for all remaining workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for the remaining workspaces.

6. monitoring Oct 20, 2026, 08:43 PM UTC

   Builds are now enabled for Hobby workspaces, in addition to Enterprise and Pro. We are working to resume builds for all remaining workspaces next. Deploys triggered while builds were paused will need to be triggered again once builds are back for your workspace. We'll share another update as we resume builds for the remaining workspaces.

7. resolved Oct 20, 2026, 08:56 PM UTC

   Builds have resumed for all workspaces and are completing normally. This incident is now resolved. If you triggered a deploy, pushed to GitHub, or restarted a service while builds were paused, please trigger it again. Those were not queued during the pause and will not start on their own. Cron jobs scheduled during the pause did not run, and will continue from their next scheduled time. We're sorry for the disruption

Read the full incident report →

Started Oct 13, 2026, 04:12 PM UTC· resolved Oct 13, 2026, 05:00 PM UTC

1. investigating Oct 13, 2026, 04:12 PM UTC

   We are aware of an issue causing builds to take longer than usual. Users may experience extended build times. We are actively investigating and will provide updates as we learn more.

2. identified Oct 13, 2026, 04:35 PM UTC

   We have identified an issue affecting build infrastructure in US West and are investigating a potential cause. Our team is working on a fix and scaling capacity in the region. Users in US West may experience builds taking significantly longer to complete. Users in other regions are not affected. We will provide updates as we learn more.

3. identified Oct 13, 2026, 04:39 PM UTC

   We have identified the root cause of the build slowness in US West and are rolling out a fix. Build times are beginning to improve as the fix is deployed. Users in US West may still experience builds taking longer than usual while the fix propagates. Users in other regions are not affected. We will provide a further update once the fix is fully in place.

4. monitoring Oct 13, 2026, 04:45 PM UTC

   Build times in US West are returning to normal. We are monitoring the situation and will mark this incident as resolved once we have confirmed sustained recovery. Users in other regions are not affected. We will provide a further update shortly.

5. resolved Oct 13, 2026, 05:00 PM UTC

   The issue affecting build times in US West has been resolved. Build times have returned to normal and the queue has cleared. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Oct 10, 2026, 01:34 AM UTC· resolved Oct 10, 2026, 01:39 AM UTC

1. investigating Oct 10, 2026, 01:34 AM UTC

   We're investigating reports of station.railway.com being unavailable

2. resolved Oct 10, 2026, 01:39 AM UTC

   This incident has been resolved

Read the full incident report →

Started Oct 09, 2026, 09:29 PM UTC· resolved Oct 09, 2026, 10:07 PM UTC

1. investigating Oct 09, 2026, 09:29 PM UTC

   We are aware of an issue affecting builds and deployments that use images from Docker Hub. Affected builds or deploys may fail with a "429 Too Many Requests" error when pulling images. We are actively investigating and will provide updates as we learn more.

2. identified Oct 09, 2026, 09:49 PM UTC

   We've identified that this is caused by an ongoing incident with Docker Hub, which is causing image pulls to fail. Builds and deployments that use Docker Hub images may fail until this is resolved. Images from other registries are not affected. You can follow Docker's updates here: https://www.dockerstatus.com/incidents/01M4HA1E00AH6NXA276AW0CK2V We're monitoring closely and will share an update as pulls recover.

3. monitoring Oct 09, 2026, 10:03 PM UTC

   Docker Hub has resolved the issue on their side and image pulls are succeeding again. Builds and deployments that use Docker Hub images should now complete normally. If a deployment failed during this incident, please redeploy it. We're monitoring to make sure everything stays stable.

4. resolved Oct 09, 2026, 10:07 PM UTC

   The issue affecting image pulls from Docker Hub has been resolved: https://www.dockerstatus.com/incidents/01M4HA1E00AH6NXA276AW0CK2V. Builds and deployments that use Docker Hub images are completing normally. If you had a deployment fail during this window, redeploying it should go through.

Read the full incident report →

Started Oct 05, 2026, 03:37 PM UTC· resolved Oct 05, 2026, 04:12 PM UTC

1. investigating Oct 05, 2026, 03:37 PM UTC

   We are aware of an issue affecting the Railway dashboard. Users may experience slow load times or difficulty accessing the dashboard. We are actively investigating and will provide updates as we learn more.

2. monitoring Oct 05, 2026, 03:57 PM UTC

   We are seeing recovery in dashboard response time and will continue to monitor this incident. We will provide updates as recovery completes.

3. resolved Oct 05, 2026, 04:12 PM UTC

   The dashboard loading issues have been resolved. The disruption was caused by API pods experiencing high event loop delays, leading to slow response times and liveness probe failures. We scaled up capacity to restore normal performance. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Oct 05, 2026, 02:55 PM UTC· resolved Oct 05, 2026, 04:13 PM UTC

1. investigating Oct 05, 2026, 02:55 PM UTC

   We are aware of an issue affecting builds triggered by GitHub. Users may experience builds queuing or taking longer than usual to start. We are actively investigating the root cause and will provide updates as we learn more.

2. identified Oct 05, 2026, 03:40 PM UTC

   We've identified the issue and are working on a fix. We will continue to provide updates as we learn more.

3. monitoring Oct 05, 2026, 03:52 PM UTC

   We are seeing recovery and the build queue is continuing to drain. GitHub-triggered builds may still take longer than usual to start while we work through the remaining backlog. We will provide another update as we make further progress.

4. resolved Oct 05, 2026, 04:13 PM UTC

   The issue affecting GitHub-triggered builds has been resolved. The build queue has fully drained and builds are processing normally across all regions. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Oct 04, 2026, 02:47 AM UTC· resolved Oct 04, 2026, 06:23 AM UTC

1. investigating Oct 04, 2026, 12:34 AM UTC

   We are aware of an issue affecting attached storage performance for some users in US West. Users may experience slow services and databases, queries taking longer than expected, deploys that are slow to become healthy, or intermittent crash loops. We have identified the cause and are actively working to restore normal performance. We will provide updates as we learn more.

2. identified Oct 04, 2026, 04:50 AM UTC

   We have identified the cause of the storage performance degradation affecting some users in US West and are actively working to resolve it. We will continue to provide updates as we make progress.

3. monitoring Oct 04, 2026, 06:08 AM UTC

   Storage performance in US West continues to improve. Latency is gradually decreasing as we work through the remaining remediation steps. We are actively monitoring and will provide another update once we have more to share.

4. monitoring Oct 04, 2026, 06:14 AM UTC

   Storage performance in US West has returned to normal. Latency is back to baseline and write operations have resumed at expected levels. We are continuing to monitor to confirm stability. If you are still experiencing issues, please reach out to support at https://station.railway.com.

5. resolved Oct 04, 2026, 06:23 AM UTC

   The storage performance issue affecting some users in US West has been resolved. Latency has returned to baseline and storage operations are back to normal levels. We apologize for any inconvenience this caused. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Oct 03, 2026, 04:55 PM UTC· resolved Oct 03, 2026, 07:33 PM UTC

1. identified Oct 03, 2026, 11:43 AM UTC

   We have identified an issue causing some hosts in US West to become unresponsive. Services and databases running on those hosts may be unreachable or fail to connect, and redeploys of affected services may stall. We are restarting the affected hosts, and services will come back automatically as each host recovers. Users with affected services will receive an email and an in-app notification. We will provide updates as we learn more.

2. monitoring Oct 03, 2026, 05:21 PM UTC

   All affected hosts in US West have been restarted, and services running on them are recovering. Users with affected services have been notified by email and in-app. If one of your services is still unavailable, redeploy it once from your dashboard. If that doesn't resolve it, please reach out at station.railway.com.

3. resolved Oct 03, 2026, 07:33 PM UTC

   The issue affecting services and databases in US West has been resolved. We apologize for any disruption. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Oct 02, 2026, 04:53 PM UTC· resolved Oct 02, 2026, 05:17 PM UTC

1. investigating Oct 02, 2026, 04:53 PM UTC

   We are aware of intermittent connectivity issues affecting some services hosted. Users may have experienced slower response times or brief connectivity disruptions. We are actively applying network-level mitigations and are monitoring to confirm full recovery. We will provide updates as we learn more.

2. resolved Oct 02, 2026, 05:17 PM UTC

   Dismissed as a notice. No impact.

Read the full incident report →

Started Sep 30, 2026, 03:06 PM UTC· resolved Sep 30, 2026, 03:34 PM UTC

1. investigating Sep 30, 2026, 03:06 PM UTC

   We're investigating an issue causing the dashboard to load slower than usual, along with some auth issues causing users to be disconnected. We are investigating this incident and will post updates here as we know more.

2. monitoring Sep 30, 2026, 03:21 PM UTC

   We're seeing recovery and are continuing to monitor this incident.

3. resolved Sep 30, 2026, 03:34 PM UTC

   The issue causing dashboard slowness and auth timeouts has been resolved. Error rates have returned to normal levels. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Sep 30, 2026, 07:34 AM UTC· resolved Sep 30, 2026, 07:57 AM UTC

1. monitoring Sep 30, 2026, 07:48 AM UTC

   We are aware of an issue that caused domains hosted on Railway to return 404 errors. The issue lasted approximately 5 minutes and has since been mitigated, this is a post facto report. We are investigating the root cause and will provide updates as we learn more.

2. resolved Sep 30, 2026, 08:17 AM UTC

   The global routing service provided a `not-found` response after a rollout of a network config change. The system self healed after the config change led to errors. Unfortunately, this led to observed impact to new connections to Railway hosted workloads for 5 minutes. There is no further and ongoing impact. The Networking team will be working on a full root cause and we will update this status report with a published cause.

Read the full incident report →

Started Sep 29, 2026, 03:29 PM UTC· resolved Sep 29, 2026, 07:15 PM UTC

1. investigating Sep 29, 2026, 03:29 PM UTC

   We are aware of an issue affecting our API that is causing slow or stuck deployments for some users. We are actively investigating and working to restore normal operations. We will provide updates as we learn more.

2. monitoring Sep 29, 2026, 06:37 PM UTC

   We are seeing recovery and are monitoring this incident. Hobby deployments have been re-enabled.

3. resolved Sep 29, 2026, 07:15 PM UTC

   The issue affecting our API and causing slow or stuck deployments has been resolved. A period of elevated load on our API caused a backlog to build in our deployment queue faster than it could drain. We applied several fixes to improve how our deployment system handles backpressure and temporarily paused new deployments for Hobby-tier projects while the queue recovered. All deployments have since resumed and are processing normally. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Sep 23, 2026, 01:24 PM UTC· resolved Sep 23, 2026, 03:13 PM UTC

1. investigating Sep 23, 2026, 01:24 PM UTC

   We are aware of an issue causing builds to take longer than expected in EU West (Amsterdam). Users in this region may experience builds progressing slowly or taking longer to start. We are actively investigating and will provide updates as we learn more.

2. investigating Sep 23, 2026, 01:53 PM UTC

   We have identified a possible issue with our deployment system in EU West that may be causing builds to queue and take longer than expected. We are continuing to investigate and working to resolve the issue. We will provide another update as we learn more.

3. identified Sep 23, 2026, 02:13 PM UTC

   We have identified the root cause as an issue with our deployment system in EU West that was causing builds to queue and take longer than expected. We are working to resolve this and will provide another update as we make progress.

4. monitoring Sep 23, 2026, 02:52 PM UTC

   We are continuing to monitor the situation following our fix. Build times in EU West (Amsterdam) are returning to normal and the queue is clearing. We will provide a further update shortly.

5. resolved Sep 23, 2026, 03:13 PM UTC

   Build times in EU West (Amsterdam) have returned to normal and the issue has been resolved. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 31, 2026, 03:31 PM UTC· resolved Aug 31, 2026, 04:12 PM UTC

1. investigating Aug 31, 2026, 03:31 PM UTC

   We are aware of an issue affecting the creation of storage buckets and bucket access keys. Users attempting to create new buckets or access keys may experience failures. We are actively investigating the root cause and will provide updates as we learn more.

2. resolved Aug 31, 2026, 04:12 PM UTC

   The issue affecting storage bucket creation has been resolved. Requests are processing normally again. We apologize for any inconvenience this caused. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 29, 2026, 01:38 AM UTC· resolved Aug 29, 2026, 02:18 AM UTC

1. investigating Aug 29, 2026, 01:38 AM UTC

   We are aware of an issue affecting some services hosted in our US West region. Users may experience services that are unavailable, stuck restarting, or experiencing slow connectivity. We are actively investigating this issue. We will provide updates as we learn more.

2. investigating Aug 29, 2026, 01:45 AM UTC

   We have isolated the issue to our storage infrastructure in US West. Affected services may experience problems starting up, slow or unavailable storage, and degraded private network connectivity. We are actively working to resolve the storage issue. We will provide updates as we learn more.

3. monitoring Aug 29, 2026, 02:08 AM UTC

   We have identified the root cause of the storage and networking issues affecting some services in US West. A hardware fault in our physical infrastructure caused degraded connectivity to our storage cluster. We have isolated the affected hardware, taken it out of rotation, and are seeing recovery. We will continue to monitor and provide updates as services stabilize.

4. resolved Aug 29, 2026, 02:18 AM UTC

   The storage and networking issues affecting some services in US West have been resolved. The hardware fault in our physical infrastructure has been isolated and removed from rotation, and all services have recovered. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 28, 2026, 11:59 PM UTC· resolved Aug 29, 2026, 03:38 AM UTC

1. investigating Aug 28, 2026, 11:59 PM UTC

   We are aware of an issue causing deployments to take longer than normal to initialize. Users may experience delays when starting new deployments. We have identified a potential cause and are actively working to restore normal behavior. We will provide updates as we learn more.

2. monitoring Aug 29, 2026, 12:20 AM UTC

   We have identified the cause of the delay: a networking issue on a single host in our infrastructure caused a backlog of deployments to queue up. We have removed the affected host from rotation and are scaling additional capacity to work through the backlog. Deployments are beginning to progress again. We will continue to monitor and provide an update once things have fully returned to normal.

3. investigating Aug 29, 2026, 12:37 AM UTC

   We are continuing to investigate an issue with deployment initialization. While we identified and removed an affected host from rotation, some of our deployment workers are experiencing instability as they work through the backlog of queued deployments. We are actively working to stabilize the deployment system and clear the backlog. We will provide further updates as we make progress.

4. investigating Aug 29, 2026, 03:05 AM UTC

   We continue to work through a backlog of queued deployments. Our deployment workers have stabilized following configuration changes, and throughput is gradually returning to normal levels. Some deployments may still experience delays as the backlog clears. We are actively working to reduce the remaining queue. We will provide further updates as we make progress.

5. monitoring Aug 29, 2026, 03:33 AM UTC

   Deployments are continuing to recover. We have stabilized our deployment pipeline and cleared most of the backlog of queued deployments. Throughput has returned to nominal levels and new deployments are progressing through the queue. Some delays may still be experienced as the remaining backlog fully clears. We are actively monitoring and will provide a further update shortly.

6. resolved Aug 29, 2026, 03:38 AM UTC

   Deployment delays have been resolved. Our deployment pipeline has stabilized. The backlog of queued deployments has been cleared, and throughput has fully returned to normal. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 20, 2026, 06:43 PM UTC· resolved Aug 20, 2026, 06:44 PM UTC

1. monitoring Aug 20, 2026, 06:43 PM UTC

   We had an incident where deploys were delayed in AMS for a short period. We are now back to normal deploy times and are watching the situation closely.

2. resolved Aug 20, 2026, 06:44 PM UTC

   We had an incident where deploys were delayed in AMS for a short period. We are now back to normal deploy times and are watching the situation closely.

Read the full incident report →

Started Aug 20, 2026, 03:27 PM UTC· resolved Aug 20, 2026, 06:20 PM UTC

1. investigating Aug 20, 2026, 03:27 PM UTC

   We are aware of an issue causing deployments to queue and take longer than usual to progress. Users may experience delays in deployments starting or completing. We are actively investigating the root cause and will provide updates as we learn more.

2. identified Aug 20, 2026, 03:56 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We are actively working to mitigate the impact and restore normal deployment throughput. We will provide further updates as the situation develops.

3. identified Aug 20, 2026, 04:15 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We are actively working to mitigate the impact and restore normal deployment throughput. As we do this deployments will be temporarily paused at times and slower. We will provide further updates as the situation develops.

4. identified Aug 20, 2026, 05:29 PM UTC

   We have identified that a Google Cloud infrastructure issue is contributing to deployment delays. Our backend services experienced elevated internal errors from Google Cloud beginning around 14:53 UTC, which caused our deployment processing pipeline to become congested. We have made adjustments and it is starting to improve but still delayed. We will provide further updates as the situation develops.

5. monitoring Aug 20, 2026, 05:31 PM UTC

   The deployment pause has been lifted and the backlog of queued deployments is clearing. New deployments are being accepted and processing again, though some delays may persist as the queue continues to drain. We are continuing to monitor the situation and will provide further updates.

6. resolved Aug 20, 2026, 06:20 PM UTC

   Deployments are operating normally. The backlog of queued deployments has cleared and deployment times have returned to expected levels. The root cause was a Google Cloud infrastructure issue beginning around 14:53 UTC that caused elevated errors in our backend services, leading to congestion in our deployment processing pipeline. We temporarily paused new deployments to prevent further backlog buildup while we worked to restore normal operations. The Google Cloud issue has since resolved and our systems have recovered. We apologize for the disruption. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 18, 2026, 11:19 PM UTC· resolved Aug 19, 2026, 02:17 AM UTC

1. investigating Aug 18, 2026, 11:19 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. investigating Aug 19, 2026, 12:40 AM UTC

   We are continuing to investigate and are narrowing down cause of delayed builds. Thanks for patience.

3. investigating Aug 19, 2026, 01:01 AM UTC

   We are continuing to investigate and are narrowing down cause of delayed builds. Thanks for patience.

4. investigating Aug 19, 2026, 01:01 AM UTC

   We are continuing to investigate and are narrowing down the cause of delayed and failing builds. Thank you for your patience.

5. identified Aug 19, 2026, 01:16 AM UTC

   We have identified a load issue within our infrastructure affecting the ability for deployments and builds to progress. We have restored builds to Pro users, and are working to get to full capacity for all customers. We will continue to provide updates as the situation develops.

6. monitoring Aug 19, 2026, 01:47 AM UTC

   Update: we are now seeing recovery of all build queues, however, a second order impact of the build queue is API response times increasing. API performance should restore once the queue is cleared. Trial/Hobby/Pro/Enterprise builds are all active and resumed. We'll monitor the situation and will provide further updates as we learn more.

7. resolved Aug 19, 2026, 02:17 AM UTC

   We have observed recovery of builds and API back to nominal. Builds are progressing for everyone on the platform.

Read the full incident report →

Started Aug 18, 2026, 09:45 PM UTC· resolved Aug 18, 2026, 10:40 PM UTC

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.

Read the full incident report →

Started Aug 17, 2026, 07:50 PM UTC· resolved Aug 17, 2026, 09:52 PM UTC

1. investigating Aug 17, 2026, 07:50 PM UTC

   We are aware of an issue causing deployments to remain in a queued state longer than usual. Users may experience delays before their deployments begin. We are actively investigating the root cause and will provide updates as we learn more.

2. monitoring Aug 17, 2026, 09:25 PM UTC

   We have deployed a fix for delayed deployments and they are improving. We are monitoring closely.

3. resolved Aug 17, 2026, 09:52 PM UTC

   The issue causing deployments to remain queued longer than usual has been resolved. Deployment times are returning to normal across all regions. We apologize for any inconvenience. If you continue to experience issues, please contact support at https://station.railway.com.

Read the full incident report →

Started Aug 17, 2026, 01:59 PM UTC· resolved Aug 17, 2026, 09:29 PM UTC

1. investigating Aug 17, 2026, 01:59 PM UTC

   Automatic deployments, pr environments, and anything relating to GitHub may be heavily delayed or fail. They are currently investigating this issue. https://www.githubstatus.com/incidents/zkxwbgr0cnmx

2. identified Aug 17, 2026, 04:46 PM UTC

   GitHub has identified the issue and is working on a fix.

3. monitoring Aug 17, 2026, 07:52 PM UTC

   GitHub has seen slight recovery and is monitoring results before resolving.

4. resolved Aug 17, 2026, 09:29 PM UTC

   GitHub is reporting that they're fully operational again.

Read the full incident report →

Started Aug 14, 2026, 04:05 PM UTC· resolved Aug 14, 2026, 04:22 PM UTC

1. investigating Aug 14, 2026, 04:05 PM UTC

   We are aware of an issue affecting logs and metrics. Users may experience delays or gaps in log and metric delivery. We are actively investigating and will provide updates as we learn more.

2. identified Aug 14, 2026, 04:08 PM UTC

   We have identified the issue and are working on a fix.

3. monitoring Aug 14, 2026, 04:16 PM UTC

   We have implemented a fix and have seen full recovery. We are monitoring the results

4. resolved Aug 14, 2026, 04:22 PM UTC

   We have seen consistent full recovery. This incident is now resolved

Read the full incident report →