Could be.

Or could be that the recent 12 months of 100x increase in code and activity is more than they had planned for when they last did capacity planning.

Vibe-coders, many of them here, often boast about the insane amount of KLoC/hour they can generate and merge.

There may be other problems but as someone who's somehow ended up integrating Git into a service twice in my career without even trying that hard to find a reason (it turns out it's weirdly handy in quite a few situations, god I wish it were implemented as a library and not a pile of Perl and shit, and yes I know about libgit2) and has looked into some of Git's and Gitlab's posts about their architectures over the years though the lens of having fought a few of the same beasts, an Azure migration was very obviously going to make things worse.

It wasn't the migration to Azure that completely borked their PR UI.

yeah, ai slop rush

everyone builds off vibes and moves fast! like no, if you are a mature company you don't need to move fast, in fact you need to move slow

the only thing that can kill e.g. github is if they move fast and break things like they do recently