Resolved after 5 minutes, affecting Railway (Dashboard — railway.com), on May 6, 2025.
We rolled out a change where we dropped a column unsafely. While the new deploy was rolling out (\~5 minutes), old deploys, the ORM we used automatically queried the old field. As a result, some small % of users who hard refreshed (and had to load project state) may have seen a 404 briefly. We're rolling out a lint rule to catch this in the future. Apologies
Affected components
Update timeline
- identified May 06, 2025, 07:35 PM UTC
We rolled out a change where we dropped a column unsafely. While the new deploy was rolling out (\~5 minutes), old deploys, the ORM we used automatically queried the old field. As a result, some small % of users who hard refreshed (and had to load project state) may have seen a 404 briefly. We're rolling out a lint rule to catch this in the future. Apologies
- resolved May 06, 2025, 07:40 PM UTC
This incident has been resolved.
Your product runs on more than Railway
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services