a month ago
Continously seeing scheduling build on Metal builder "builder-sskgan" and no builds actually run.
Updating variables also does not work.
New deployments not working - old ones dont work either.
17 Replies
a month ago
I am also having this problem
a month ago
likewise, builds stalling
a month ago
Same here, builds failing
a month ago
it looks like it is some type of problem with github connection possibly as it says there is a problem with that connection
onagent
it looks like it is some type of problem with github connection possibly as it says there is a problem with that connection
a month ago
Can confirm that both my failing builds are connected via github.
onagent
it looks like it is some type of problem with github connection possibly as it says there is a problem with that connection
a month ago
yeah, possible, the repo is connected via github. Their Metal builders are also having issues
a month ago
same here. also connected via github
a month ago
same. here
a month ago
Same here - connected via github
a month ago
Same here - github issue somehow. Builds failing. Obvs.... in the middle of some important changes... Any @railway support to undertand ETA?
a month ago
Same here: [ERROR] ##NOT-AUTHORIZED## repository not authorized finally showed up for one deploy.
a month ago
Same, deploys are failing. Possibly related to https://www.githubstatus.com/incidents/gxycch3076xk, but I'm stuck on scheduling a builder...
mchristopher
Same, deploys are failing. Possibly related to https://www.githubstatus.com/incidents/gxycch3076xk, but I'm stuck on scheduling a builder...
a month ago
yup confirmed https://status.railway.com/incident/8BVRVAAM
a month ago
Sorry everyone. It's my fault. I made a large pull request in my private repo. It broke GitHub. Live and learn.
a month ago
Builds for services that deploy from GitHub started failing around 22:40 UTC because GitHub is having an API outage on their side. The build gets scheduled but we can't pull your code from GitHub, so it fails with no build logs. Your running services aren't affected.
We're tracking this at https://status.railway.com/incident/8BVRVAAM and GitHub's own status is at https://www.githubstatus.com/incidents/gxycch3076xk. Once GitHub recovers, pushing a new commit or redeploying will work again with no action needed on your end. If you need to ship right now, the CLI still works because it uploads your code directly: run railway up from your project directory.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago




