3 ms·
That's all very understandable up to a point. But what I find more than a little disconcerting is that they had paying customers complaining about this issue fo
by fauigerzigerk 14y ago
That's all very understandable up to a point. But what I find more than a little disconcerting is that they had paying customers complaining about this issue for years but were "unable" to find the root cause or were unwilling to explain it. After one customer's comlaint was picked up by a wider public it took them barely a day or two to find out and explain what was going on.
In other words, as long as it suited them financially, they couldn't be bothered analyze, document and fix the issue properly. Now they come out apologizing because the reputational damage is greater the money they make from letting customers use their stupid architecture. This is a classic really.
Time for a refund.
- boundlessdreamz 14y agoActually, didn't the customer find out the problem? They identified random routing as the culprit. Also identified that new relic does not report these metrics. Also heroku told them that "requests are queued up at the dyno level". So how can they now claim that they didn't know?