I’m currently unable to connect my GitHub account to Railway. When attempting to authenticate, I consistently receive the following error:

“Error authenticating with GitHub – Problem completing OAuth login”

I also see the banner stating:

“GitHub logins or deployments may timeout due to downstream rate limits.”

Based on this message, it appears the issue is related to the ongoing
Railway <-> GitHub incident rather than any repository or permission misconfiguration on my end.

Additionally, I’m experiencing an issue specifically with my development environment deployment. I already have two environments set up:

• Main – working and deployed successfully

• Develop – previously working and deployed correctly

However, the development environment now shows the error:

“Cannot setup automatic deploys for my-app because no one in the workspace has access to it.”

This is confusing because:

• The repository access has not changed

• The application has deployed successfully before

• The main environment continues to work as expected

It seems this automatic deploy error started appearing after the GitHub authentication issues and may be related to the same incident affecting GitHub integrations.

Could you please confirm:

1. Whether both the GitHub OAuth failure and the automatic deploy access error are related to the current GitHub rate-limit incident

2. If any action is required from my side once the incident is resolved

3. Whether re-connecting the repository or re-authenticating GitHub will be necessary after the fix