Looks like it's not load that brought it down but someone posting a 340kb individual message that's triggering a bug because we didn't account for that sort of thing somewhere.

The good thing is we now have an easily reproducible case, thanks HN :)