I'd imagine the higher volume due to remote work (e.g. people collaborating more on issues and such who may have communicated in person previously) is also a co

I'd imagine the higher volume due to remote work (e.g. people collaborating more on issues and such who may have communicated in person previously) is also a contributing factor. From the sound of their earlier 'not postmortem but we'll do one soon', it sounded like they currently have a database tier that's creaking at its foundations, and I'd guess any time there's extra strain or someone pushes a fix to the GitHub codebase that adds a tiny bit of unoptimized code, it strains it past the limit.