24 days ago
Hi Railway team,
I’m currently on the Railway trial with the $5 trial credit and I’m still within the 30-day trial period. My total usage is only around $0.05–$0.06, so I should still have almost the full credit remaining.
However, during the current deployment/build incident (“builds are slow to progress”), my project started behaving inconsistently. At different points, deployments would sometimes work and sometimes fail, and now Railway is showing that my “trial is maxed out,” even though my usage clearly does not reflect that.
The main issue is that Railway is now blocking deployments from my GitHub repository, so I’m unable to push my updated code live. My latest code is already successfully pushed to GitHub, but Railway is stuck on the previous deployment because new deployments are being blocked by this “trial maxed out” message.
This appears to be related to the current infrastructure/build incident because I experienced similar behavior earlier during the same incident.
Could someone please check whether my account/project was incorrectly flagged or temporarily locked during the incident, and help restore deployment access to the active trial?
Thank you!
1 Replies
Status changed to Awaiting Railway Response Railway • 24 days ago
24 days ago
What you're seeing (trial showing maxed out, $0 balance or $0 usage, the usage page failing to load, or deploys not triggering) is a display and routing issue tied to the May 19 GCP outage, not your actual account state. Our metrics pipeline is still recovering from that incident, and when those queries time out the dashboard incorrectly falls back to zero values and a maxed-out trial. Your real credit balance, trial period, and project state are intact in our billing system, no credits were consumed during the outage. The team is actively rolling traffic off the impacted system and the dashboard should self-correct once it stabilizes. We're sorry for the disruption.
Status changed to Awaiting User Response Railway • 24 days ago
17 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 17 days ago