We can't change, merge, or reassign which identity an account resolves to. This is a security boundary that protects the account, not a limitation we can override with ownership proof. The two paths back to the account with your projects are both on your side: recover access through whichever provider is linked to that original account (GitHub, Google, or email) if it has become inaccessible, or sign in with another method that was already linked to it. If every method you try lands in this empty workspace instead, the original account may be linked to a different set of credentials than the ones you're currently using. Sorry we can't do more from here.

Thanks, but this is an automated response and it hasn't resolved my issue — I'd like a human to take a look, as this needs someone who can inspect the account records.

To be clear about what I'm asking: I'm not asking you to override a security boundary. My projects are live right now and actively redeploying from a specific GitHub repo, so the owning account clearly exists — I just need help identifying which login identity owns it, because all of my sign-in attempts land in an empty workspace instead.

Concrete details to help you locate the account:

• Billing email on that account: veinops@gmail.com
• Most recent invoice: DKOHT4BQ-0005 (receipt 2401-2944), $9.48 paid May 8 2026, Hobby plan

Could you check which login identity (GitHub / Google / email) owns the workspace that contains that project and deploys from that repo? If it's a matter of my logins being linked to a duplicate record created during the outage, that's exactly what I need help fixing. I'm happy to prove ownership by creating a public GitHub repo with a name you specify, or via my billing records.

We understand the frustration, and we hear the distinction you're drawing. Disclosing which login identity is linked to a given account is itself within the security boundary, even with billing or repo proof of ownership, because that is exactly the information an attacker with proximity to the account would need. The paths outlined in the earlier reply are the only routes to reach the original workspace.

Understood, I accept that's inside the security boundary.

Here's the narrower, verifiable problem I'd like help with. I've now tested cleanly: I fully signed out of Railway first, then signed in via email, Google, and GitHub, for both of my emails (veinops@gmail.com and nexvilocal@gmail.com). Every one of those six attempts authenticates successfully but lands in an empty workspace.

Meanwhile, that same subscription is still active and billing me. My most recent invoice is DKOHT4BQ-0005 (receipt 2401-2944), $9.48 charged to veinops@gmail.com on May 8, Hobby plan , and the projects tied to it are still deploying. So I'm being charged for a workspace I can authenticate against but cannot see.

I'm not asking who owns it. I'm asking you to check, on your side, whether my billing/subscription record and my projects are attached to the same account record that my logins now resolve to, or whether my sign-ins are resolving to a different, empty record than the one being billed. If those have become separated, please reattach my access to the account I'm paying for, or tell me the exact step to reach it.

I'm glad to complete any verification you require. I just want access to the account I'm being billed for.

Project ID please.

Project ID: d3d05117-58f2-46d8-85d2-9e079d298676

That project is not owned by any email that you have mentioned.

Please understand that is the absolute most I am able to tell you.

So, you have simply been logging into the wrong Railway accounts.

Thank you, you gave me a clue that I didn't think was a possibility, and you are right, I used a totally different email to login and I have acess now. Thank you so much for your patience and to hold the line to protect my account from unauthorized access.