My app was slower, but I didn't have the 10% error rate specified by the SLA to qualify as downtime. Did you? If you did, you can submit a ticket and I believe you will get a refund for the whole day's billing. Don't hold me to that I haven't read the SLA lately. But you have to submit to receive a refund they aren't automatic, and they are for error rates over 10% of requests (I'm pretty sure) so my app that is snappy just ran slow I don't qualify. If your app is slower it may.
Brandon Wirtz BlackWaterOps: President / Lead Mercenary Description: http://www.linkedin.com/img/signature/bg_slate_385x42.jpg Work: 510-992-6548 Toll Free: 866-400-4536 IM: [email protected] (Google Talk) Skype: drakegreene YouTube: <http://www.youtube.com/blackwateropsdotcom> BlackWaterOpsDotCom <http://www.blackwaterops.com/> BlackWater Ops <http://www.cloudonastring.com/> Cloud On A String Mastermind Group -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of philburk Sent: Tuesday, January 31, 2012 4:10 PM To: Google App Engine Subject: [google-appengine] Re: is app engine down? I'm seeing a huge number of deadline errors and our app failing to server, hr datastore Hi Marzia, Thanks for the status update. BTW, if the problem was so severe that you had to shut down a datacenter and are offering billing credits, then why does the status page today show no problems? <http://code.google.com/status/appengine> http://code.google.com/status/appengine How bad do things have to get before they are listed on the problem page? Maybe you could show a finer grained status. The two valued "No significant issues" vs "Service disruption" does not communicate much. Maybe you could use a series of emoticons that ranged from ecstatic to happy, content, sad or suicidal. ;-) Thanks, Phil On Jan 31, 11:28 am, Marzia Niccolai < <mailto:[email protected]> [email protected]> wrote: > Both today and yesterday, there was a networking issue in one of the > datacenters serving High Replication applications that caused > increased datastore latency and elevated error rates. We responded by > stopping app engine from serving out of the affected datacenter until > the problem was resolved. > > If you have a paid HRD app and you feel the SLA has been violated for > your app, you can file a request for billing credits here:https://docs.google.com/a/google.com/spreadsheet/formResponse?hl=en_U.. . > > -Marzia > > > > > > > > On Tue, Jan 31, 2012 at 9:33 AM, Alexis < <mailto:[email protected]> [email protected]> wrote: > > Also get big issues simultaneously with all our apps 10 min ago. > > Lot of errors, drop in requests/sec while peak of active instances. > > > <http://code.google.com/status/appengineshowed> http://code.google.com/status/appengineshowed an "anomaly" for > >Python, but now it's back to "Elevated" and I guess it'll disappear > >as usually... > > > -- > > You received this message because you are subscribed to the Google > > Groups "Google App Engine" group. > > To post to this group, send email to <mailto:[email protected]> [email protected]. > > To unsubscribe from this group, send email to > > <mailto:[email protected]> [email protected]. > > For more options, visit this group at > > <http://groups.google.com/group/google-appengine?hl=en> 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 <mailto:[email protected]> [email protected]. To unsubscribe from this group, send email to <mailto:[email protected]> [email protected]. For more options, visit this group at <http://groups.google.com/group/google-appengine?hl=en> 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.
<<image001.jpg>>
