Yeah, true. In this case, I'm sure most teams did what mine did, and waited for the outage to be resolved. The development workflow and CI/CD is so tightly coupled to the Git remote, it would have taken a while to create and switch to another remote.

I once used another alternative: each member of the team runs git-daemon on their desktop to export their local repository, and adds the repositories exported by the other members of the team as git remotes. You can merge a coworker's master branch to your master branch whenever you want to get their changes (and the changes they already merged), which makes for a chaotic but fun development experience.