[01:13:10] <WikiForgeRelay>	 <quanchquanch0805_99625> the issue was already fixed
[01:26:36] <notaracham>	 testing relay
[02:44:32] <WikiForgeRelay>	 <bwm0> Hi all, I’m back 🙂
[02:44:47] <WikiForgeRelay>	 <lichmaster98> Hello
[14:57:00] <WikiForgeRelay>	 <epic eye> Folks, bad news to say, WikiForge is down again
[15:00:24] <WikiForgeRelay>	 <notaracham> pinging @Site Reliability Engineers, slows and repeated 503s are hitting WT wikis as well
[18:34:13] <WikiForgeRelay>	 <nionlogos18> Casual WikiForge
[19:26:37] <WikiForgeRelay>	 <tali64, replying to nionlogos18> I remember this happening a lot with Miraheze back in the day, but Miraheze doesn't throw errors often anymore; guess it transferred to WikiForge after the split
[19:28:32] <WikiForgeRelay>	 <agentisai> We don't throw errors that often either but I'm at a loss as to why all mw*'s are at 100% CPU
[20:09:36] <WikiForgeRelay>	 <agentisai> I think it's fixed
[20:10:07] <WikiForgeRelay>	 <agentisai> Please, someone do me a favor, if in the future I say "all mw*'s are at 100% CPU and I don't know why", tell me "check Memcached"
[20:10:45] <WikiForgeRelay>	 <notaracham> Memcached, it's already memcached. 🤣
[20:11:17] <WikiForgeRelay>	 <agentisai> always
[20:11:30] <WikiForgeRelay>	 <agentisai> and the problem is that when it crashes, it's not immediately visible
[20:11:41] <WikiForgeRelay>	 <agentisai> like MediaWiki won't error out, it'll just be really slow
[20:29:30] <WikiForgeRelay>	 <novamcneary97> minor avid error