Here's something interesting I came across:
https://blogs.oracle.com/ksplice/attack-of-the-cosmic-rays
Cosmic rays may well cause ordinary people headaches it seems!
BUMP a month and a half later: You know, that bit-flipping thing popped into my head on Monday when our oscilloscope stopped working, but it quickly became clear that the nature of the problem was different.
But anyway, I'm here to describe my rather interesting internet situation. As I mentioned in the You Game last week, my DSL started acting up. Dad fiddled the junction box which was fairly precarious and may have been disrupted by the felines, but it still seemed to be in trouble. I reckoned the router might be overheating.
Anyway, since Dad works for the ISP, he decided on Tuesday to disconnect everything, go into work and check our line. Attenuation turned out to be 61 dB! Seemingly because the line was never really properly repaired after Storm Darwin, way back in 2014. So he got it repaired, but still there were issues.
Seems the router itself was having trouble. Any time Dad connected to the WiFi with his phone the DSL went down. And my mother was having constant interruptions to the online work she was doing on her laptop.
So so far, it seems to have been a complete clusterfail: the cat-disrupted junction-box, the terrible line quality, and the router itself. Then on top of that came another coincidence. The ISP sent us a new router in the post on Thursday! I had been saying that our router was really old and in need of replacement, and they apparently agreed!
So today I got around to setting up the new router. Everything seemed to be going grand, and I was able to set up the port-forwarding without too much bother. Except the port-forwarding wasn't actually being honoured.

A bit of Googling revealed that the ISP "didn't support port forwarding" and that apparently their vendor-specific firmware for this router hardcoded it to listen on ports 80 and 443 even if the user asked it to forward them to a server. So the router is completely unsuitable for someone who runs a self-hosted website.
I put back the old router, and started thinking about the problems it was having. It seemed to give out whenever someone was using the internet via WiFi. So if we could separate the WiFi router from the DSL router, we could salvage the operation. Well, we have two routers, so why not give it a go!
I turned on the new router, connected to one PC and isolated from the rest of the network to avoid conflicts. I logged into it using the PC and changed its IP address, and turned off its DHCP server, so it was no longer in charge of the network.
At this point I reconnected it to the rest of the network, and sure enough, it seemed to be able to bridge the PC I had connected to it, and its WiFi clients, to the rest of the network, which was being run by the old router. It took a bit of rebooting to get every machine on board with this weird setup, but it seems to work!
I do wonder how long it'll last though. Sure, it's just the WiFi that's taking out the DSL on the old router now, but soon it could be the Ethernet too, in which case it'll be game over. Then I guess we'll have to look into getting a third-party router or something…