Re: Heroku down time today, about 30 minutes total
Three 9's are triple 6's if you turn them upside down. \m/ On Fri, Oct 29, 2010 at 2:52 AM, Al wrote: > So, 3 nine's is what to expect from Heroku? > > > On Oct 28, 3:50 am, Peter Marklund wrote: > > 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 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 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 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:008/4/2010 17:51:000:45:00 > > > > > > > SEPTEMBER - Total unavailable minutes: 28 > > > > > > > 9/13/2010 8:46:009/13/2010 8:55:000:09:00 > > > > > 9/13/2010 14:26:009/13/2010 14:36:000:10:00 > > > > > 9/21/2010 1:16:009/21/2010 1:21:000:05:00 > > > > > 9/28/2010 22:26:009/28/2010 22:30:000:04:00 > > > > > > > OCTOBER - Total unavailable minutes so far: 45 > > > > > > > 10/4/2010 15:41:0010/4/2010 15:51:000:10:00 > > > > > 10/5/2010 11:56:0010/5/2010 12:01:000:05:00 > > > > > 10/26/2010 12:16:0010/26/2010 12:26:000:10:00 > > > > > 10/26/2010 14:41:0010/26/2010 14:46:000:05:00 > > > > > 10/26/2010 15:21:0010/26/2010 15:36:000: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 > 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 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 > 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 > > > > > > > >>> . > > > > >>> 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. > > > >
Re: Heroku down time today, about 30 minutes total
We're seeing 99.90% uptime on an app deployed in June. N On Oct 29, 6:52 am, Al wrote: > So, 3 nine's is what to expect from Heroku? > > On Oct 28, 3:50 am, Peter Marklund wrote: > > > > > > > > > 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 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 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 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 > > > > > 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 > > > > >> 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 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 > > > > >>> > 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 > > > > >>> . > > > > >>> 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 > > > >
Re: Heroku down time today, about 30 minutes total
So, 3 nine's is what to expect from Heroku? On Oct 28, 3:50 am, Peter Marklund wrote: > 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 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 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 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 > > > > 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 > > > >> 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 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 > > > >>> > 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 > > > >>> . > > > >>> 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. > > > > > -- > > > > You received this message b
Re: Heroku down time today, about 30 minutes total
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 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 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 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 > > > 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 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 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 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 > > >>> . > > >>> 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. > > > > -- > > > 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. > > >
Re: Heroku down time today, about 30 minutes total
As much as it sucks when your site goes down, Heroku is doing a better job taming EC2 than I was. I've had my stuff on EC2 for some time and was ready to bail after a lot of frustration, but decided to take Heoku for a whirl. What EC2 offers is pretty cool, but you have to put a lot of work in to deal with recovering from EC2's own problems, like instances dropping off. I lost five in a year. Heroku abstracts all that for Rails apps. On Wed, Oct 27, 2010 at 12:01 AM, David wrote: > Growing pains. They'll get it resolved. > > > On Tue, Oct 26, 2010 at 6:03 PM, Shane Becker > 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 >> . >> 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 > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- = Brandon Casci Loudcaster http://loudcaster.com = -- 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.
Re: Heroku down time today, about 30 minutes total
Growing pains. They'll get it resolved. On Tue, Oct 26, 2010 at 6:03 PM, Shane Becker 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 > . > 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku down time today, about 30 minutes total
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 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 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 > > 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 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 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 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 > >>> . > >>> 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. > > > -- > > 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. > > --+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.
Re: Heroku down time today, about 30 minutes total
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 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 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 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 > . > 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.
Re: Heroku down time today, about 30 minutes total
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 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 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku down time today, about 30 minutes total
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 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Heroku down time today, about 30 minutes total
> 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
