I agree with Jason on all counts. I wasn't even following their twitter feed and it didn't occur to me to look there -- I still think of Twitter as a channel for superficial gossip, not mission-critical support alerts. And considering *Twitter's* notorious issues with downtime, I think it's a dangerous precedent for Heroku not to post to other channels -- like perhaps this Google Group, not to mention their own web site -- when things go South.
- A On May 16, 11:23 am, Jason McCay <[email protected]> wrote: > Heroku looks to be back up...but for our app, we were unreliable since > 7PM CST last night (first report of customer issues) and it seemed > like we were completely down from at least 7AM CST this morning until > around 1:00 PM CST today. So, a couple of observations: > > 1. That was a long period of being down. > > 2. The Heroku team really has to do a better job of communicating with > people when something like this happens. I attempted to find updates > through multiple channels (twitter, blogs, irc, and finally this > google group) and Heroku had said nothing. Then, after about five > hours of being down, they finally start responding on twitter. > > I love you Heroku...but I have to be able to trust you, too. :) > > Jason > > On May 16, 12:36 pm, Alex Chaffee <[email protected]> wrote: > > > > > A further report... as of 10:30 am my server is totally unavailable as > > well. > > > "heroku logs" returns a blank line. > > > "heroku db:pull" returns "Internal server error" > > > Hitting the web site gives the ouchie Japanese guy. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
