[Karunamon]

>By misrepresents you mean that the end users didn't exactly understand how underlying architecture worked

Uh.. no.

Heroku claimed to use intelligent routing, they used random routing. And then covered it up with their monitoring tools.

How in the name of crap can you blame this on the user?! Did you even read the Rap Genius writeup on this problem? If I were in their position, I would be utterly livid.

[res0nat0r]

I read the article. I wouldn't call it "covering up". It didn't explain everything going on, just like all kinds of things that go on behind the scenes everyday at AWS that users don't understand.

Define "intelligent routing". Maybe it is intelligent to route 85% of your requests to /dev/null. Can you sue because your performance sucks in your application use case? Most normal people eval their provider, try to get answers from support (which rapgenius have done here), and if the answers aren't up to snuff or the performance isn't whay they think it should be for what they are paying they move to another provider. They don't sue their provider for being "slow".

[joesb]

> Define "intelligent routing".

At least Heroku themselves define "intelligent routing" such that the request will only be given to the free Dynos. Their random routing does not do that.