4 ms·
Cynical view: By making people jump through hoops to make the request, a lot of people will not bother. Assuming they only refund the service costs for the hou
by zizee 7y ago
Cynical view: By making people jump through hoops to make the request, a lot of people will not bother.
Assuming they only refund the service costs for the hours of outage, only the largest of customers will be owed a refund that is greater than the cost of an employee chasing compiling the information requested.
For sake of argument, if you have a monthly bill of 10k (a reasonably sized operation), a 1 day outage will result in a refund of around $300, not a lot of money.
The real loss for a business this ^ size is lost business from a day long outage. Getting a refund to cover the hosting costs is peanuts.
- idunno246 7y agofor your example, one day would be about 3% of downtime. My understanding of their sla, for the services ive checked with an sla, a 3% downtime is a 25% credit for the month's total, or $2500, assuming its all sla spend. In this outage's case you might be able to argue for a 10% credit on affected services for the month, figuring 3.5 hours down is 99.6% uptime. but i still agree, it cost us way more in developer time and anxiety than our infra costs, and could have been even worse revenue impacting if we had gcp in that flow
- zizee 7y agoGood point, I stand corrected/educated. From GCP's top level SLA: https://cloud.google.com/compute/sla https://cloud.google.com/compute/sla 99.00% - < 99.99% - 10% off your monthly spend 95.00% - < 99.00% - 25% off your monthly spend < 95.00% - 50% off your monthly spend
- ohashi 7y ago<95%... that's catastrophically bad.
- chrisseaton 7y ago> For sake of argument, if you have a monthly bill of 10k (a reasonably sized operation), a 1 day outage will result in a refund of around $300, not a lot of money. Probably literally not worth your engineer's time to fill in the form for the refund.