A whole other part of this argument that could be made is about the inherent assumption that a ping timeout is caused by an event that only affects one machine.
I'll admit to sending a couple of the messages that made Linksys routers restart. I also set up automatic k-lines on Snoonet for these very strings, years ago
There are events that may affect more than one machine which are not netsplits.
e.g. an ISP with common users experiences an outage, an IRC client with common users has a bug, common users within the same time zone have automated system updates run at the same time, the IRC server experiences an upstream network disruption affecting only some routes, a regional power outage occurs, a hosted bouncer service with common users has an outage, etc, etc, etc...