Manually redeploying the page a couple of times “fixed” the issue. Would be nice if the deploy could automatically restart if it encounters this specific error.
Thanks for raising this - we’ve had a handful of reports of this today and whilst we do have retry logic in place it does seem that in these instances it hasn’t been enough and you end up seeing this message. We’re investigating nevertheless.
We’ve made some changes now which we hope will mitigate this entirely - adding retries as well as some DNS caching for github.com - we’re monitoring the changes to make sure they are successful,