We're sorry for the trouble. We're aware of an ongoing incident, "GitHub is experiencing elevated error rates", which is affecting automatic deployments, PR environments, and anything relying on GitHub. GitHub is currently investigating on their end. You can follow updates here: status page.

Please involve a human being from the team, not the bot. Thanks

The error is always the same at build stage: repository forbidden.

Apologies for the frustration. Your builds are failing because GitHub is currently experiencing elevated error rates, which is impacting auto-deploys, PR environments, and any GitHub-dependent operations on our platform. We don't have a resolution timeline from GitHub yet, but you can track their progress here: status page.

I love AI but I hate bots when they reply in 2 milliseconds when you need concrete human intervention. So where are the humans on the other side of the screen?

We completely understand the frustration, and apologies for the bot responses earlier. The "repository forbidden" error is coming directly from GitHub's API, which is currently experiencing elevated error rates on their side. There is unfortunately nothing we can do to accelerate their resolution, but your builds will recover automatically once GitHub restores normal operations. You can track their progress at our incident page or directly on GitHub's status page.

Your incident page has not moved an inch since 13:59 UTC, 2+ hours ago...

I love being a Railway advocate, but in my opinion, a major incident thread shouldn’t remain silent for two hours. GitHub’s status page isn’t any more helpful. Given the scale at which you operate, don’t you have direct contacts on their team?

Our incident page reflects what GitHub has communicated so far, and we update it as they provide new information. For more frequent progress updates, GitHub's own status page is the best source. Builds will resume automatically once GitHub restores normal API operations.

Well, the AI assistant isn't very helpful :)

Apologies for the repetition, and we hear your feedback on the communication experience. The honest answer is that we're dependent on GitHub's resolution here, and there is no new information to share yet beyond what's on their status page. Your builds will resume the moment their API recovers.

Same unhelpful communication at their end. We definitely live in the matrix.

We hear you, and the frustration is completely warranted. GitHub's own updates confirm they're still at roughly 50% error rates on repository content downloads, which is what's blocking builds on our side. Unfortunately there's nothing more we can share until GitHub publishes a meaningful status change. Your builds will recover automatically once they do.

I also have the same question, when it will be fixed? Clients are waiting and changes aren't deploying to server.

This is on Github’s side. Railway isn’t able to do anything about this.