If it seemed like the Internet was slow or broken on Monday, it wasn’t your imagination. It really was.
When applications and web sites fail, there are circumstance you simply couldn’t foresee, but other times, if you had done the little things, maybe you could minimized the damage of an outage, and in those cases, it really could be your fault.
Sometimes things go wrong that are completely out of your control including natural disasters and freaks of nature, but that doesn’t mean powerful people won’t use the situation to point the finger of blame at you.
When RIM had a three-day outage earlier this month, it was embarrassing and damaged the company’s reputation, but I’m sure one outcome it never expected was a lawsuit.
When Blackberry went down last week, it hurt its diminishing reputation, but the failure to communicate for more than two days didn’t help matters. It’s worth noting that my informal research found the few users I asked weren’t affected by the outage.
If you’re monitoring software isn’t monitoring your systems all the time, you could be missing crucial problems in between polling times, and that can have big consequences.
We reported that last week’s Southwest blackout was caused by monitoring hardware, but it turns out, maintenance on a series capacitor was the most likely culprit according to utility officials.
Up time statistics are only so useful. What really matters is how much the down time affects end users and how quickly you recover from an issue.
When Master Card’s web site experienced intermittent outages last week, the easy answer was to point to hackers, but it turned out it was a problem with an Internet service provider, proving more often than not the problem isn’t external.