If you read the chronology, it appears that if they had done this at the
beginning, the incident would have been over two hours sooner.
On Oct 29, 2012, at 5:13 PM, Benjamin Possolo wrote:
> On Saturday, October 27, 2012 9:28:44 AM UTC-7, Joakim wrote:
> You could probably do something like thi
You could probably do something like this if you serve through CloudFlare, but
it would be much nicer if we could set a page for this in the app config. I'll
file a feature request tomorrow, unless someone else wants to or has already
done so. Suggestions for specifications would be appreciated.
You can configure an error page for all the "normal" error conditions
(out of quota, exceptions that hit the top level, other 500 errors,
etc). It wouldn't have helped you today though.*
https://developers.google.com/appengine/docs/python/config/appconfig#Custom_Error_Responses
(there is a Java
Any idea how you would handle requests staying in pending for 24 minutes?
This happened to me today:
https://www.evernote.com/shard/s8/sh/ad3b58bf-9338-4cf7-aa35-a255d96aebbc/4b90815ba1c8cd2080b157a54d714ae0
This server gets about 7 to 12 request per second and usually handles them
in ~200ms. Bu
The only way you could have done that this time is by re-directing your DNS to
someplace completely non-google.
On Oct 26, 2012, at 6:18 PM, Benjamin Possolo wrote:
> Hey all. Like most everyone else here. My application was affected by the GAE
> downtime this morning.
>
> I would like to kn
Hey all. Like most everyone else here. My application was affected by the
GAE downtime this morning.
I would like to know if there is a good mechanism for detecting this sort
of failure in the future so that my application can automatically throw up
a Maintenance Page.
Normally I would have an
