Regardless with hosting option you choose you will have downtime. I
have found more often than not the reason is to do with infrastructure
like power, networking, hardware, routing etc. that will most likely
be out of your control. I think the downtime I've seen with Heroku is
tolerable and you shouldn't necessarily assume you'll have less
downtime if you move somewhere else.

Peter

On Oct 27, 9:46 pm, oma <ole.morten.amund...@gmail.com> wrote:
> unexpected downtown is way different than planned downtown. This is
> really discomforting. I'm not looking forward in moving my production
> app to more stable place... heroku should really answer this.
>
> On Oct 27, 7:19 pm, Jimmy Thrasher <ji...@jimmythrasher.com> wrote:
>
> > Interesting.  So, back of the envelope, from a dev perspective:
>
> > ruby-1.8.7-p302 > elapsed = (Time.local(2010,10,26,16) -
> > Time.local(2010,8,1)) / 60
> >  =>124800.0
> > ruby-1.8.7-p302 > (elapsed - 45 - 28 - 45) / elapsed
> >  => 0.999054487179487
>
> > About 99.9% uptime over the elapsed time.
>
> > It's still way cheaper for me to use Heroku, but the cost of 30 minutes of
> > downtime in a month is fairly low.  Folks with higher uptime requirements
> > are likely just going to have to shell out the $$$ no matter which way you
> > slice it.
>
> > Jimmy
>
> > On Wed, Oct 27, 2010 at 12:54 PM, John Norman <j...@7fff.com> wrote:
> > > Below is the data I have for one app (similar data from two other apps).
>
> > > So, for September, 28 minutes of downtime . . . better than 3 nines:
> > >http://en.wikipedia.org/wiki/High_availability#Percentage_calculation
>
> > > But I would much rather report to my customers official data from Heroku.
>
> > > The times below are central time zone, I think.
>
> > > AUGUST - Total unavailable minutes: 45
>
> > > unavail at           avail at             elapsed
> > > 8/4/2010 17:06:00    8/4/2010 17:51:00    0:45:00
>
> > > SEPTEMBER - Total unavailable minutes: 28
>
> > > 9/13/2010 8:46:00    9/13/2010 8:55:00    0:09:00
> > > 9/13/2010 14:26:00    9/13/2010 14:36:00    0:10:00
> > > 9/21/2010 1:16:00    9/21/2010 1:21:00    0:05:00
> > > 9/28/2010 22:26:00    9/28/2010 22:30:00    0:04:00
>
> > > OCTOBER - Total unavailable minutes so far: 45
>
> > > 10/4/2010 15:41:00    10/4/2010 15:51:00    0:10:00
> > > 10/5/2010 11:56:00    10/5/2010 12:01:00    0:05:00
> > > 10/26/2010 12:16:00    10/26/2010 12:26:00    0:10:00
> > > 10/26/2010 14:41:00    10/26/2010 14:46:00    0:05:00
> > > 10/26/2010 15:21:00    10/26/2010 15:36:00    0:15:00
>
> > > On Wed, Oct 27, 2010 at 9:53 AM, Jimmy Thrasher 
> > > <ji...@jimmythrasher.com>wrote:
>
> > >> I'd be curious to find out what the actual uptime percentage is, and what
> > >> it would cost you to maintain that on a different platform with 
> > >> comparable
> > >> services.  :)
>
> > >> Jimmy
>
> > >> On Wed, Oct 27, 2010 at 9:55 AM, JDeville <jeffdevi...@gmail.com> wrote:
>
> > >>> Al, I'm afraid Heroku's had a fair bit of downtime since I've joined
> > >>> earlier this year.  The status link mattsly gave you paints a pretty
> > >>> grim picture.  I figure I'll probably have to come up with something
> > >>> else once my site's uptime becomes important to me.  I'm hoping they
> > >>> stop adding new features, and instead pour themselves into stability.
>
> > >>> On Oct 27, 8:11 am, mattsly <matt...@gmail.com> wrote:
> > >>> > You can browse the incident archive here:http://status.heroku.com/past
>
> > >>> > Most of the issues seems to be related to tooling, but  there was at
> > >>> > least one other case of app outage earlier in the month (Oct. 4)
>
> > >>> > Does Heroku publish uptime numbers?  Does anyone running an app in
> > >>> > production (I'm still not yet...) have app uptime numbers they're
> > >>> > willing to share?
>
> > >>> > On Oct 26, 7:03 pm, Shane Becker <veganstraighte...@gmail.com> wrote:
>
> > >>> > > > How can we be sure this won't happen again?
>
> > >>> > > No
>
> > >>> --
> > >>> You received this message because you are subscribed to the Google 
> > >>> Groups
> > >>> "Heroku" group.
> > >>> To post to this group, send email to her...@googlegroups.com.
> > >>> To unsubscribe from this group, send email to
> > >>> heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com>
> > >>> .
> > >>> For more options, visit this group at
> > >>>http://groups.google.com/group/heroku?hl=en.
>
> > >> --
> > >>+1-919-627-7546
>
> > >> --
> > >> You received this message because you are subscribed to the Google Groups
> > >> "Heroku" group.
> > >> To post to this group, send email to her...@googlegroups.com.
> > >> To unsubscribe from this group, send email to
> > >> heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com>
> > >> .
> > >> For more options, visit this group at
> > >>http://groups.google.com/group/heroku?hl=en.
>
> > >  --
> > > You received this message because you are subscribed to the Google Groups
> > > "Heroku" group.
> > > To post to this group, send email to her...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/heroku?hl=en.
>
> > --+1-919-627-7546

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to