Your workspace still shows a $5.00 credit balance on our end, so the trial was not actually consumed. This looks like a transient platform-side issue that incorrectly flipped the workspace to an inactive state. Please try a hard refresh or logging out and back in to clear any stale dashboard state, and let us know if it's still showing as maxed out after that.

And coming back, I saw that many indeed have this same exact issue...

I have the same problem here.

Maxed out, but still have credits.

Here is a print of the usage page:

No, this did not help for my case. Other users and I still need help.

I also got this problem. beside that, the project doesnt look what I've pushed to github.

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.

The problem is resolved?

Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.

It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.

You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY

If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c

Feel free to respond if your question has not been addressed.

I've got the exact same problem. In addition there is no automatic udate via github.

Same problem.

Hey all,

Just want to check- we had some issue with our metrics since the outage and have rolled out a fix that should sort this out.

Are you all still seeing issues here? if so, let me know and I'll forward back up to the team.

It seems to be fixed - for me. thx. :)