Lemmy.world has been down between 02:00 UTC and 05:45 UTC. This was caused by the database spiking to 100% cpu (all 32 cores/64 threads!) due to inefficient queries been fired to the db very often.
I’ve collected the logs and we’ll be checking how to prevent this. (And what caused this)
lemmy.world is a test environment for Lemmy developers… 😅 Jokes aside, issue is an issue.
Well, as pretty much the biggest instance, it provides the best data for load-testing. 🫣
All Lemmy instances are test environments right now. It’s just that lemmy.world is being tested the hardest.