When i attempt to access my apps homepage (babel.heroku.com), i get
the following message:
Application Error
An error occurred in the application and your page could not be
served. Please try again in a few moments.
When I attempt to access the log, I get:
Dave-Dalys-MacBook:sinatra_gwap
We're experiencing some problems right now -- keep an eye on
http://status.heroku.com/ for updates.
On Apr 21, 5:27 am, Daithi havingab...@gmail.com wrote:
When i attempt to access my apps homepage (babel.heroku.com), i get
the following message:
Application Error
An error occurred in the
I think that when there is general AWS instability affecting Heroku, the
default error message might provide a word or two that attributes the issue
to Heroku's responsibility.
When a customer sees the attached, it would be nice to have some cover.
--
You received this message because you are
Hi Ben,
Can you please provide some more color on the connectivity issues
mentioned on status.heroku.com? I have rarely seen networking issues
take this long to be resolved in a production environment.
Thanks,
Rohit
On Apr 21, 5:08 am, Ben Scofield b...@heroku.com wrote:
We're experiencing
Amazon AWS seems to be the root cause.
http://status.aws.amazon.com/?a
And the ensuing Hacker News thread is here:
http://news.ycombinator.com/item?id=2469838
--
Arun Thampi
Sent with Sparrow
On Thursday, April 21, 2011 at 10:56 PM, Rohit Dewan wrote:
Hi Ben,
Can you please provide some
Furthermore, the status page could be available as a RSS to be able to keep
an eye on it easily. What do you think? (also send mails or sms, but maybe
as a second step).
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send
I wonder if it has anything to do with this: http://status.aws.amazon.com/?a
-- Pito
On Thu, Apr 21, 2011 at 11:08 AM, Steve Smith st...@scsworld.co.uk wrote:
Rohit, These issues are affecting pretty much everyone on the EC2 US-East
region. It's actually something out of Heroku's hands. If you
Michel Pigassou wrote:
Furthermore, the status page could be available as a RSS to be able to keep
an eye on it easily. What do you think? (also send mails or sms, but maybe
as a second step).
Actually there is already a RSS feed available :)
--
You received this message because you are
It is Pito, we're in the UK so we've been up a while we have, been watching
this for a while now. Unfortunately things have been playing up on AWS for a
quite a few hours. I think there will be some questions for Amazon once things
are resolved.
On 21 Apr 2011, at 16:24, Pito Salas
Curiously, my site was up for a long time during theses issues but is now
down.
Do we know exactly which of the red line items on
http://status.aws.amazon.com/?a are the cause?
jeff
On Thu, Apr 21, 2011 at 10:39 AM, Steve Smith st...@scsworld.co.uk wrote:
It is Pito, we're in the UK so we've
According to Amazon, the N. Virginia cluster is the one experiencing an
outage.
Does anyone know why Heroku not able to redeploy onto another cluster? In
general, it would seem prudent to spread applications across the various
clusters so all apps do not suffer an outage when a single cluster is
Is there a reason why Heroku doesn't spread the dynos across us-west-1
and us-east-1?
K.
---
http://blitz.io (down at the moment)
http://twitter.com/pcapr
On Thu, Apr 21, 2011 at 8:50 AM, Rohit Dewan dew...@gmail.com wrote:
According to Amazon, the N. Virginia cluster is the one experiencing an
or even Europe ;)
Neil Middleton
http://about.me/neilmiddleton
On Thursday, 21 April 2011 at 17:02, kowsik wrote:
Is there a reason why Heroku doesn't spread the dynos across us-west-1
and us-east-1?
K.
---
http://blitz.io (down at the moment)
http://twitter.com/pcapr
On Thu, Apr
Touche! What I would like to see is to have proxy.heroku.com resolve
to different AWS regions with an option to distribute the dynos
geographically. Now that would totally rock.
heroku region:add us-east-1 :)
And if the region in which the dyno is deployed is available as an
ENV, even better.
Last Few updates:
*ISSUE:* We are continuing to work with our service provider to restore
outstanding connectivity issues. We will continue to update every half hour
or as new information becomes available.
APR 21, 2011 – 16:25 UTC – 16 MINUTES AGO
*UPDATE:* We are continuing to work with our
Ha! Love your new signature!
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this
On Apr 21, 11:50 am, Rohit Dewan dew...@gmail.com wrote:
Does anyone know why Heroku not able to redeploy onto another cluster? In
general, it would seem prudent to spread applications across the various
clusters so all apps do not suffer an outage when a single cluster is
affected.
I agree
I'm a total lurker on this list, but I give a strong second to Eric's
comment.
Whatever the technical explanation/root-cause turns out to be this is not
acceptable platform behavior.
Very troubling.
--sp
On Thu, Apr 21, 2011 at 2:06 PM, Eric Anderson e...@pixelwareinc.comwrote:
On Apr 21,
Here's what you want -- from: http://status.aws.amazon.com/
The last three provide the most information.
1:41 AM PDT We are currently investigating latency and error rates with EBS
volumes and connectivity issues reaching EC2 instances in the US-EAST-1
region.
2:18 AM PDT We can confirm
I have never bothered to create a custom error page. I'm curious for
the heroku users that did, do you see your custom error page or is
everyone seeing the Application Error page listed at the beginning of
this post.
--
You received this message because you are subscribed to the Google Groups
We created a custom error page and are seeing the heroku generic instead of
our prettiness. Sad...
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from this group, send email
Yes, quite *sad*.
In this cases the only solution is to have a backup hosting/server and
do a DNS change. I solved this way.
On 21 Apr, 21:19, chris mcclellan...@gmail.com wrote:
We created a custom error page and are seeing the heroku generic instead of
our prettiness. Sad...
--
You received
I've been using the Zerigo add-on to manage our DNS, and it's actually
a pretty slick service. But suppose Heroku is having an hours-long
outage, let's say. Just spitballin' here. And suppose I want to point
my domain somewhere else temporarily. I could do that with Zerigo, but
since I always get
Exactly. Me, too.
So I think Heroku needs to help us slobs out and take credit for this outage
with an error page that says: Amazon done it.
On Thu, Apr 21, 2011 at 2:19 PM, chris mcclellan...@gmail.com wrote:
We created a custom error page and are seeing the heroku generic instead of
our
Seriously, +1 for this. Wish we could put up nicer screens for our
clients. People have no idea what's going on all day.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to heroku@googlegroups.com.
To unsubscribe from
At first I was annoyed by the error message, but when I saw it on
www.heroku.com, I didn't feel so bad any more.
Yes, it is confusing for the users.
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to
Btw, I understand stuff happens, it just hurts.
Sent from my iPhone
On Apr 21, 2011, at 4:19 PM, Joe Sak j...@joesak.com wrote:
Seriously, +1 for this. Wish we could put up nicer screens for our
clients. People have no idea what's going on all day.
--
You received this message because
27 matches
Mail list logo
