Quick update- I've filled an issue internally to investigate this and have been working with the GAE Billing engineering team to troubleshoot.
The public issue for this is Issue #36201328 <https://issuetracker.google.com/issues/36201328>; I suggest everyone impacted click the "Me too!" button to stay connected as we make updates to the issue. The public issue will be the most up-to-date source of information, but I'll also update this thread once that issue is resolved. On Thu, Mar 16, 2017 at 9:39 AM, Lawrence Mok <[email protected]> wrote: > I can determine the date that happen to me is from 1st March 2017. > > This is because most of my instance runs exactly 24 hours a day and by > calculations I can determine the charges should start very clear to 1st > March 2017. > > Once you can confirm you're a Google staff I will provide you the project > IDs > > > On Thursday, March 16, 2017 at 11:57:00 PM UTC+8, joshuamo wrote: >> >> Based on the screenshots above and the multiple reports in this thread, >> something seems off (or unexplained) with regards to billing for GAE >> Standard / Free tier apps. Can one of the affected in this thread reply >> privately to me with the following information? >> 1. Project ID of an affected project >> 2. A date that you noticed the change in frontend instance hours billed >> for >> >> That will help us target the investigation and, hopefully, bring us to a >> quicker understanding of the issue. >> >> >> On Thursday, March 16, 2017 at 12:17:46 AM UTC-7, Somaya Sarathbabou >> wrote: >>> >>> +1 here. >>> >>> We have the same issue for the App to be billed, for the past few >>> months/years, we have never been billed for this usage, now why all of a >>> sudden, if its going to be charged users shd be made aware by a proper >>> announcement or given us some time where we could think of migrating our >>> apps. >>> >>> We have been using GAE for the past 5 years without a single charge. As >>> all others mentioned, no point in chking with the Billing Team, as they ll >>> ding dong for 100days left without any proper solution.I also have prior >>> experience with the Billing Team with several ding dongs and finally I gave >>> up and i have all the trail emails history too. >>> They dont know the tech part thats their issue, pity on them >>> >>> Plz check this urgently *and do a CREDIT REVERSE for all of us on time. >>> in fact, a commercial goodwill should also be provided for all of us, as we >>> are wasting our time here in detecting several Google based bugs*. >>> >>> >>> >>> *App Engine Frontend Instances: 133.418 Hours (Source: xxxx]) -$1.27* >>> I can give my project ID in PM, if required for investigation purposes. >>> >>> Pl let us know faster for this Charging issue. >>> I m sure lot of other people are still unware of this Billing Issue, i >>> cant imagine how will they respond to, once they see the month end invoice >>> and the Support Calls made to Google. >>> >>> Thanks, >>> Ss >>> >>> On Thursday, March 16, 2017 at 7:05:06 AM UTC+8, Lawrence Mok wrote: >>>> >>>> George, this is very irresponsible for your answer. You should report >>>> back to your boss for this case instead. Or I will be reporting to your >>>> boss. >>>> >>>> If you just take 5 seconds to look at the screen shots carefully, you >>>> would see the $0.01 is from Code and Static File Usage, not from App Engine >>>> Instance Hours. >>>> >>>> >>>> >>>> On Wednesday, March 15, 2017 at 11:05:45 PM UTC+8, George (Cloud >>>> Platform Support) wrote: >>>>> >>>>> On the "usage history" page with the vertical list of usage values, >>>>> where you land if you navigate to app engine --> quotas --> view usage >>>>> history in the dev. console, there is an information label on top saying: >>>>> "These costs are estimates based on App Engine list prices." Estimates may >>>>> be wrong to some extent, as they are what they are named: only estimates, >>>>> in contrast to guaranteed and double-checked values. In your case the >>>>> estimates are mostly 0.01. In all cases, these values are provided for >>>>> orientation and best-effort basis, just to provide an estimate. They are >>>>> not meant to be compared with final values. >>>>> >>>>> The "Google Cloud Platform Billing Support" page >>>>> <https://support.google.com/cloud/contact/cloud_platform_billing> may >>>>> help you to contact Customer support for billing, and clarify similar >>>>> cases. More information is to be found on the "Billing and Payments >>>>> Support" documentation page >>>>> <https://cloud.google.com/support/billing/>. >>>>> >>>> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-appengine. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/google-appengine/b777f1ae-9587-4d73-9fb8- > aa18aeb7e16a%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/b777f1ae-9587-4d73-9fb8-aa18aeb7e16a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Josh Moore | Cloud Solutions Engineer | [email protected] | -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAOvpJmUGd9Hp5SC-5whycbRx0cpipUexsrPCeBGMxPedUMj8nA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
