mastodon.social has once again caught up with real-time. I haven't received the new machine for the database yet (seems like the technical issues unfortunately overlapped with some bank holidays; hopefully tomorrow) but I managed to find a way to optimize some code that seems to have helped. Thank you for being patient, and again, I'm really sorry you couldn't experience Mastodon at its best the past few days on here.