I appreciate Heroku's apology, but it: 1) Understates the problem – It affects not only Bamboo, but all thin (and other non-concurrent web servers) on Cedar. A

I appreciate Heroku's apology, but it: 1) Understates the problem – It affects not only Bamboo, but all thin (and other non-concurrent web servers) on Cedar. And since thin is the default on Cedar, the problem affects all apps on Cedar by default 2) Understates how long they knew about it – I notified Heroku about the problem INCLUDING the simulation results 3 days before the blog post came out and yet the apology claims they didn't know about the problem until seeing the blog post.