7 days ago
Hi,
I'm an existing Railway customer and I'd like to add a collaborator to one of my projects, but the invite can't be accepted while new signups are paused.
The situation:
- I sent a workspace invite from my project on 24 October.
- The invitee doesn't have a Railway account yet. When they try to accept it via GitHub, they get: "Error authenticating with GitHub — Sign ups are currently disabled. Please try again later."
- The invite expires on 30 October.
I understand signups are paused while you focus on existing customers after the recent incident, and I'm not asking you to lift that generally. Either of these would unblock us:
- Allow this single account to be created. It isn't a cold signup from outside — it's an invited collaborator on an existing, paying workspace.
- Or just tell us roughly when signups are expected to resume, so we know whether to wait or to reissue the invite after this one expires.
Happy to share the project name and the invitee's email privately rather than post them in a public thread — just let me know where to send them.
Thanks for your time, and good luck with the cleanup.
2 Replies
Status changed to Awaiting Railway Response Railway • 7 days ago
6 days ago
New account signups are paused while we focus on existing customers after the recent incident, and we don't have a date to share for when they will reopen (October 21 incident status page).
The error your collaborator sees appears when they sign in with an identity that isn't linked to an existing Railway account. Because of that, there's no need to send the project name or their email here. If the invite lapses before signups resume, you can send a new invite once they're able to create an account.
Status changed to Awaiting User Response dizzydes90 • 6 days ago
an hour ago
Signups have reopened, so your collaborator can retry creating their account. The reopening currently requires a paid account to use Railway. Sorry this delayed their access.