Although I repeatedly asked you not to take this conversation to "Who's fault is the downtime", you still do so!
Again, my problem is that when it is Google's fault, there's no one to talk to - Can you argue anything relevant to this point please? Amazon had a week downtime, but THERE WAS SOMEONE TO TALK TO! Whenever Amazon is done I receive an email from them telling me why, and how they solved it. I would be happy to continue the conversation of "is google meeting their SLA" in private. But read the subject of this email - You can't argue that on the 11th of November there was a serious issue which is not represented in the system status, and that we have not been informed any of! Regarding the points you have mentioned: 1. For 45minutes, 30% of errors, is to me 45 minutes of downtime. Since it happens during evening time when thousands of people enter my site to order lunch, and 30% of them need to refresh the site to see the welcome page and the rest suffer latency, I see it as 45 minutes. (I agree, it could be worse, but it is still bad for my brand name). 2. By definition you cannot have the uptime you talked about when Google themselves say that they have a 98.92% up time! Unless you do not have traffic during those times, which is cool for you, but we have traffic to our site all of the time. - Yoav. On Nov 20, 10:44 am, "Brandon Wirtz" <[email protected]> wrote: > I read your response. > > I don't think you read the graphs you sent. > For 45minutes they were at 30% errors. That only counts as 15 minutes of > downtime. And since it appears that only polls once every 5 min or so I'm > not sure what that means for SLA. > > You spoke of downtimes you had that weren't reported elsewhere. And you > said that you know it was GAE's fault because they didn't hit your App. I'm > saying that your "downtime" may have been misconfiguration. > > Also even if you are correct that 99.5 isn't being met since they are at > 98.2 or something along those lines, it is early in the yearly average. > > I'm all for calling people out when they have made mistakes, but my uptime > thus far is north of 99% and is likely north of 99.75% Amazon had nearly a > week of down time, they will be 2 years getting that back to an average of > 99.5. > > > > > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of trilok > Sent: Sunday, November 20, 2011 12:03 AM > To: Google App Engine > Subject: [google-appengine] Re: Google App Engine's Team Dishonesty > > Mr Wirtz, > > You have not read my response. > > All of the examples I have given are Google issues since they are presented > in the system status. > > I do know when my system is down for my fault and when it is down on > Google's fault. If you dive into the system status you will see that even by > their account they do not meet the SLA (Current availability is 98.92%. FAR > from 99.95%). > > Again, my real issue is that Google not only does not meet their SLA, but > that they do not communicate the issues transparently to their users. > > Facts are these: > > 1. Google do not meet their SLA (again, look at their stated current > availability in the system status). > > 2. When they are down on their fault, I have no way of knowing when is the > problem going to be fixed, and how are they preventing it in the future. If > I do not know the answers to those questions, how can I communicate > stability to my clients? What do I tell my paying clients when they ask me > 'when is the system going to be up again'? > > I am begging you again, do now make it a "who's fault is it that my system > is down" issue! Sadly I already think that you've diverted the conversation > to a point where I won't get any answers now > > Bottom line I would like Greg to answer: How can I continue using the GAE > when I do not get transparency regarding Google related down times (during > or after)? > > - Yoav. > > On Nov 20, 4:07 am, "Brandon Wirtz" <[email protected]> wrote: > > You sited outage numbers greater than what Greg did. If your app was > > down for your own fault then it is NOT a google issue. > > > If less than 1% experienced an outage of less than 5 minutes, and > > those apps were idle then the number of "lost" pages was likely even > lower. > > > You said they were not meeting SLA, and Not Reporting. But if your > > numbers are wrong, then we don't know that is the case. You can't > > call Google out, AND not diagnose if the problem is YOUR fault. > > -- > 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 > athttp://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.
