On Tuesday, March 13th, Boston experienced a large power outage due to a transformer fire. NStar crews arrived to the scene in mass in a heroic effort to contain the fire and get the Back Bay, Fenway and South Boston residents and businesses back online within a matter of days.
I was on Spiceworks today and ran into this conversation about 100% uptime.I had a few thoughts but am interested in what others had to say, as well. Share them below, or on Spiceworks! Most SLAs will claim 100% uptime (which most of you know is unattainable) with the provisions that “an outage doesn’t count if it is under 10 minutes” or caused by certain factors, or a host of other excuses.
Uptime SLAs are not being written to protect the customer. They are designed to shield the service provider and avoid responsibility. It should be different. I was just reading some stories of system downtime on the LinkedIn conversation “Skip Continuous Availability and High Availability. Have You Been a Victim of No Availability?” It struck me that service providers are failing to write SLAs that respond to the real costs of downtime.