Sounds like this was “resolved” on HN and CEO said this was an error, but I’m not so sure. The CEO’s response seems to imply that that communication to/from service reps is true and not made up. The original post shows they have a business practice for cases like this. Plus if the company was willing to settle from their business practice of 20% down to 5% (which in this case was 15k) then that very likely isn’t a decision a service rep could make, so you had some mid to upper level manager make that approval to write-off the $15k and decide that $5k was still owed to the company.
As far as I can tell the only error here is that someone posted about it.
Not to mention the CEO’s response from HN just says this shouldn’t have happened on free accounts, but that begs the question of would this have been any different on non-free accounts where Netlify failed to mitigate a DDoS as advertised?
Sounds like this was “resolved” on HN and CEO said this was an error, but I’m not so sure. The CEO’s response seems to imply that that communication to/from service reps is true and not made up. The original post shows they have a business practice for cases like this. Plus if the company was willing to settle from their business practice of 20% down to 5% (which in this case was 15k) then that very likely isn’t a decision a service rep could make, so you had some mid to upper level manager make that approval to write-off the $15k and decide that $5k was still owed to the company.
As far as I can tell the only error here is that someone posted about it.
Not to mention the CEO’s response from HN just says this shouldn’t have happened on free accounts, but that begs the question of would this have been any different on non-free accounts where Netlify failed to mitigate a DDoS as advertised?