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 <[email protected]> wrote: > On Saturday, October 27, 2012 9:28:44 AM UTC-7, Joakim wrote: > 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. For > example, it would probably be wise to aggressively push these error pages to > some kind of edge cache, and to make implementation easier it could be > limited to accepting a single HTML file per app. > > I think this would be a valid request. It would great if Google could just > flick a collective switch for all of our apps to render a maintenance page > when something big like this happens. > My DNS is handled by a separate hosting provider and sending a request ticket > to them would just take forever. > > I would be happy if I could just show a static HTML page with inline CSS (the > obligatory, moderately funny 500 image would be hosted elsewhere). > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/35cplEq70mYJ. > 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/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
