> You talk about git.apache.org being down, while you're willing to bring down the entire ecosystem across the board with your own special server.
If the proxy goes down, by default the command falls back to directly fetching.
If the proxy goes down, by default the command falls back to directly fetching.
For example, this should in theory work to make the google-run proxy your fourth choice, with three other proxies attempted before the google-run proxy, and with direct (no proxy) access as the fifth and final fallback:
go env -w GOPROXY=gocenter.io,goproxy.io,goproxy.cn,proxy.golang.org,direct