Changes are never just lost, when an error does happen and the action cannot be completed then it is rejected and the user notified of this so they can try what they were doing again. You have vastly overstated the severity of such issues.
Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Link to Original Source
I recently started with a company who's connectivity was slow. At first it was a "we'll fix it later" problem. A few days later, the connection went down. Not only was the data line down, but so was the voice. 2 hours later, it was resolved.
Two weeks later, the provider had a significant outage of between 12 to 14 hours (depending on who you ask). I was then informed that this wasn't the first time this happened. This was the 4th major event in 2 months. "minor" events have included bad latency and packet loss, and phone numbers that simply don't ring to the office. It was already established policy for staff to call the office phones on their cell phones every hour or so, just to make sure all the numbers would ring.
We were gentle with our phone call and letter, simply reminding them that it is unacceptable for us to have long periods of downtime during our business day. We didn't ask for reimbursement, just termination of the services. Their response was that we could cancel our contract for payment of one full year of service."