[jnsaff2]

The "network connectivity" issues are pretty funky, our ELB sometimes just gets a timeout on connecting, sometimes works fine and sometimes gives the SSL cert of another site (though always the same CN).

Edit: we are on standard AWS/ELB, not Heroku.

Edit2: seems to be working and AWS updated their status as well. However pretty scary that some of our traffic got sent to someone else's LB/servers.

[marcusr]

Similar here, direct to an instance, it runs at about full speed for 15 seconds, then stops. We can SSH in no problem, and the web logs show some people are connecting in fine.

Funny how the AWS status page still has a green tick (and a small discrete (i)) even though there's a confirmed problem.

[gtaylor]

> Funny how the AWS status page still has a green tick (and a small discrete (i)) even though there's a confirmed problem.

This really irritates me to no end. I imagine it's done to keep their numbers looking good, or because some manager is incentivized to not properly flag it as an outage.

It's pathetic that I have to do this, but I follow @ylastic on Twitter and hear about outages much faster that way.

[eknkc]

Our Elastic Beanstalk app behind an ELB gone haywire too. It has been scaling itself up and down, throwing out errors from time to time..

[marcusr]

Looks like they've fixed whatever the issue was as our networking is back to normal.