New account signups are currently paused as part of an ongoing incident, and that error appears when a sign-in would create a new Railway account rather than log in to an existing one. We can't whitelist individual GitHub accounts or reopen signups for one user, and this thread is tied to an existing account, so the GitHub identity used on that attempt is not the one that account is linked to.

You can follow the incident here: station.railway.com is unavailable. We're still monitoring it.

UNTIL WHEN WILL KUB FIX THSI PROBLEM AND BY WHAT DATE WILL IT BE RESOLVED

The update on our preliminary report says we plan to reopen signups this week: https://blog.railway.com/p/preliminary-report-october-security-incident#continuous-updates. There's no firmer date than that, and the notice at https://status.railway.com is updated when they reopen.

Your existing account doesn't need to wait for that. It's linked to the GitHub account under the same username as this one, priyambgmiffm-scrims, and it signed in successfully on October 25, a few minutes before this thread was opened. The "Sign ups are currently disabled" message only appears when the GitHub account you authorize on the login page is a different one, because that attempt tries to create a new account. Sign in with the GitHub account that's already linked and you'll land in your workspace and can deploy.

When the new account sign-up starts, will the authorization be done with the Alise email?