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.

If the question is about your own access, you don't need to wait. The account you're posting from is linked to a GitHub account and signed in successfully earlier today. The "Sign ups are currently disabled" message only appears for a sign-in that would create a new account, which includes using a GitHub account, Google account or email that isn't the one already linked to yours.

We are having the same issue, we have teammate that it couldn't sign up :S

New signups are still paused, so a teammate who doesn't already have a Railway account can't create one yet. We don't have a date to share for reopening, and the October 21 incident status page is where the pause is recorded.

If your teammate already had a Railway account before the incident, they can still log in with the exact GitHub account, Google account or email they originally signed up with. The "Sign ups are currently disabled" message only appears when the identity used isn't linked to an existing account.

So does it mean that the Oct 21 incident is not fully resolved yet? This must affect your biz a lot.

The platform-side response is done: the attackers are no longer present, and the preliminary report at https://blog.railway.com/p/preliminary-report-october-security-incident sets out what happened. The pause on new signups is a recovery step we're keeping in place for now rather than a sign of an ongoing compromise, and it's tracked on https://status.railway.com, which is where the reopening will be announced. There's still no date to share.

Is there any further updates on this. I have a new staff member that needs access to continue our dev work. Can you give any indication of when this may be fixed, as we may need to look for alternative hosting if it's going to take too long.

New signups are still paused, so your new staff member can't create a Railway account yet, and we don't have a reopening date to share.

If they already had a Railway account before the pause, they can log in with the exact GitHub account, Google account or email they originally signed up with. The "Sign ups are currently disabled" message only appears when the identity used isn't linked to an existing account.